Fixes #36880 - include LookupValue permissions in fixtures

Fixes #36759 - only call allowed transpilers

CVE-2022-3874: OS command injection via ct_command and fcct_command

Instead of allowing to call any command by changing a setting, only
allow specific paths to ct/fcct. If the user needs a different path,
they can set it via settings.yaml.

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 #35088 - Remove GCE Compute resource code

All code related to GCE compute resource
is now in Foreman Google plugin

https://github.com/theforeman/foreman_google

Fixes #4007 - updating users email to be optional (#9279)

Fixes #34305 - stop creating settings in DB (#9050)

With the setting DSL, we hold all the necessary values for settings in the memory.
We can now stop creating records for the settings in the database.

Fixes #33782 - do not use fixtures for Settings

As we no longer require settings in DB, we may drop the fixtures for settings.

Fixes #34339 - sanitize fqdn in tests

Tests were almost not using the fqdn defined in settings.yaml.test
That is quite confusing at first sight and we should not override this value by fixtures, only if overriden in the same test file.

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.

Refs #34323 - sanitize setting fixtures

Setting fixtures should not be used to override defaults for tests unless meant for every test.
If we mean to override the setting value for all tests, we should override value and not the default.