All Settings models to have app setting to make global

Models that are considered "Settings" like manufactures currently does; must have the option within application settings to force it to be global.

Details

Update application settings and logic so that "Settings" models can be forced into the global organization that has been set.

Tasks

• Add Model Knowledge Base Category to global model settings
• Add Model Ticket Category to global model settings
• Add Model Ticket Comment Category to global model settings
• Add Model Cluster Type to global model settings
• Add Model Operating System to global model settings
• Add Model Service Port to global model settings
• Add Model Project State to global model settings
• Add Model Project Type to global model settings

Requirements

• common to all tasks:

  • 🧪 Ensure Add user can add model
  • 🧪 Ensure that when set, the model is moved to the global org
  • 🧪 Ensure that only users of the global model can edit global items.

Start with application settings and the existing manufactures behavior for Settings models. Trace the model logic for the eight listed categories, then review how users add and edit global items. Done means each model can be configured as global, moves to the configured global organization when enabled, and has the requested add/edit coverage; no test files are named in the issue.