DYN-3777: disable linter choice in forbidden workspaces

[BogdanZavu]

Purpose

For now, we will only allow users to change Linter in HomeWorkspaceModels. This is temporary and we will remove this limitation in the near future.

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.
• This PR modifies some build requirements and the readme is updated

[mjkkirschner]

Can a user get into a situation where they open a custom node which is somehow set to the wrong linter and it cannot be disabled?

[BogdanZavu]

That should not be possible just yet, you can't set an active linter for a custom node workspace. Also, there is no "link" against a custom node workspace model and no processing will occur.

[saintentropy]

LGTM @BogdanZavu

[BogdanZavu]

The test failure is unrelated to this change and it passed when the build was triggered manually from Jenkins.