Support managing logger scenario rules via a custom object or setting

[jongpie]

Currently, logger scenarios can be used both for tracking, but also to control Nebula Logger's behavior (e.g., for certain scenarios, increase the logging level, etc.). This can give a lot of control in complex orgs/teams where only certain parts of the codebase may want to have increased logging (or other settings overrides).

However, this is all managed through the custom metadata typeLoggerScenarioRule__mdt - this makes it very easy to add the rules to source control & deployments, but limits teams who aren't actual admins in an org (and thus, don't have access to modify custom metadata records). In these situations, teams have to either coordinate with an actual admin in the org, or run a full deployment, just to change a scenario rule.

Either in addition to, or instead of (?), the existing LoggerScenarioRule__mdt, there should also be a custom object (or maaaybe a custom setting) that users with the LoggerAdmin permission set can manage.

• This would come at the expense of more SOQL queries needed to query the custom object (as well as some data storage), but the overall benefits may be worth it.
• Platform cache could be used to help minimize the impact of queries, though not all orgs have platform cache allocation for Nebula Logger to use.