Model/type references in other models shouldn't receive the support.class scope.

[Ultra-Instinct-05]

Description of the bug

Currently, model/type references in other models/types receive the support.class scope which is totally wrong (because they are not something that a standard library provides. Prisma Schema Language doesn't have that concept). The reason I chose it was for the coloring of model/types to be different from standard scalar types (like Int, String etc.). Ideally, it should receive something like variable.other.model.prisma based on sublimehq/Packages#1861 but variable scopes are always colorless, so it's visually straining to distinguish them.

Steps to reproduce

Refer the syntax definition.

Expected behavior

Model/type references have variable.other.model scope. We could put some steps on tweaking the color scheme to color variable.other.model the same as support.class but that's an additional wall for some.

Actual behavior

Model/type references have support.class scope.

PrismaHighlight version

1.0.2

[Ultra-Instinct-05]

On second thoughts, it might be difficult to scope it exactly as variable.other.model as in MongoDB schemas, we don't know whether it's going to be a model or a composite type,