Load projects based on bsconfig.json presence

[TwitchBronBron]

Enhances the language server to scan the project for all bsconfig.json files. If any are found, each is treated like its own bright(er)script project. If no bsconfig file is found, then the root of the workspace is treated as a bright(er)script project instead.

This will cause problems for any projects that have a root bsconfig and a nested bsconfig. The mitigation for that issue is to rename the outer (or inner) bsconfig.json to something else, like bsconfig.root.json for example.

Notable changes:

• renamed the word workspace to project in the language server in many places. Now the core item is a project, and 1 workspace can have many projects
• treat the root workspace as project only if there are no bsconfig.json files nested in the workspace folder
• don't crash language server when bsconfig.json has syntax errors
• better handling when adding/removing bsconfig.json files (i.e. load/unload projects accordingly)
• eliminates the need for vscode code-workspaces in most cases.

TODO:

• unit tests for removing and adding bsconfig.json files dynamically to a workspace
• unit test for honoring vscode files.exclude setting

[livecano]

Looks good to me!