Make the plugin global DataModel-aware

[gaymeowing]

Currently when working on a plugin the plugin global infers as just Plugin, rather than having special stuff like script does.
This leads to the issue of where I can have a folder called assets in my plugin, and to be able to access it with types I need to do script.Parent.assets instead of the cleaner alternative of plugin.assets that also doesnt rely on where the script is placed.

[JohnnyMorganz]

For my own reference: the plugin global is not accessible in ModuleScripts, according to https://create.roblox.com/docs/reference/engine/classes/Plugin.

We might want to hide the plugin global in non-Script cases as well

[JohnnyMorganz]

Actually, this is a bit harder than it first seems, as I'm not sure there is any way we can determine what instance the plugin reference points to. A plugin can either be created from the script itself, or a Folder parent, and nothing in the sourcemap really determines this

[gaymeowing]

Actually, this is a bit harder than it first seems, as I'm not sure there is any way we can determine what instance the plugin reference points to. A plugin can either be created from the script itself, or a Folder parent, and nothing in the sourcemap really determines this

plugin is sorta like how game is, where its the top most instance for everything in a plugin
with every instance in the project tree having it as an ascendant
also from what ive seen every plugin has Folder as the tree instance instead of WorldRoot in the project.json

{
	"name": "GapFill v1.3.2",
	"tree": {
		"$className": "Folder",
		"Src": {
			"$path": "src"
		},
		"Packages": {
			"$path": "Packages"
		}
	}
}

[JohnnyMorganz]

I see, I guess we could just assume the root node of the provided sourcemap and use that. It would break in cases where the sourcemap is not just the plugin (eg. It's a full game sourcemap where the plugin code is part of it), but maybe we can accept that for now.

also from what ive seen every plugin has Folder as the tree instance instead of WorldRoot in the project.json

Not necessarily true, see luau-lsp's studio plugin code in the plugin/ folder. In our case, the root is a script. Also, we could potentially serve test.project.json where the root is a game which the plugin is part of