Fixes #37039 - Honor permissions and taxonomies for host statuses

Fixes #36869 - update hosts path with current_hosts_path

Fixes #36711 - Fix searching in settings

Fixes #29939 - drop category column from settings

Settings table was holding category column to support old style of
settings, but it is now ready to be decomissioned as plugins were given
enough time.

Fixes #34866 - Settings - Like operator for name

• Allow ~ operator for name
• Fix issue with double quote in search
• Raise exception for unsupported operators :and / :or

Fixes #30861 - keep setting collections in registry

Move Setting collection registry into the setting registry.

Refs #34323 - explicit value for Rails 6.1

In c693cd9 we have worked around an issue for distinguishing between value explicitly set by user and not set.
This workaround doesn't work properly in Rails 6.1 and we should improve it to work properly.

Fixes #34328 - GraphQL use directly SettingRegistry

GraphQL was reading the settings from DB, but now we have the registry, it needs to read it from there instead.

Mutation needs to set the value through the SettingRegistry as well.

Fixes #34323 - use defaults from memory

This loads values from database only if the values are in the database.
If there is no value populated for the Setting, we want to read the default from memory.

Fixes #33935 - Cache setting categories

Every call to `@settings.category` in the index page recalculates all
the category names and labels by iterating over all settings. Since the
categories can't change in runtime, we can calculate it once and store
the list on the settings registry. We can also get the label once per...

Fixes #33791 - respect global settings precedence

In the new registry we've forgot to force the global values precedence.
This forces the global values to be respected.

Fixes #32893 - use setting DSL for General category

This uses our new DSL to define the General settings, this showcases how
to use the new DSL and other categories should follow in the same
release.

Fixes #33347 - Fix settings index API

Fixes #33280 - category for DSL defined settings

Fixes #31638 - Adds host status overview page

refs #32287 - Restrict search operators for Settings

Search method from 'setting index loads from registry' PR [0]
support only few search operators, `SearchBar` component
at Settings page should not display other unsupported operators

[0] https://github.com/theforeman/foreman/pull/8438

Fixes #32415 - access only through SettingRegistry

Update and read the settings through SettingRegistry.
Adds a layer between controller and Model.
SettingRegistry is proxying the value parsing method to the model.

This lifts blocker for settings without DB record.

Fixes #32286 - new settings definition DSL

Introduces a new DSL to define settings, so we don't need to define
STI classes for every setting category and we have more control over
settings from the plugins.

Fixes #32287 - setting index loads from registry

The values provided on the Setting index page are now served from
registry, with simple search API, that can be easily improve to support
more querying features.

Fixes #30862 - introduce SettingRegistry (#8002)

SettingRegistry keeps all the setting information as set of SettingPresenters in memory.
This registry should be the public API for accessing setting values and keeps all the information about settings.
That will allow dropping all information except `name` and `value` from database....

Refs #31285 - use Ruby 1.9 style Hash

Fixes #31285 - setting timestamps for API

Presenter doesn't include Setting timestamps, what resulted in a regressision,
the timestamps were not present for the API responses anymore.
This brings the timestamps back temporarily.

Fixes #30860 - introduce SettingPresenter (#8001)

Introduces SettingPresenter, that should keep all the information about setting.
This aims to keep such information only in the code and remove them from the DB.

This only prepares the ground for future drop of this information from DB....