Optionally enforce scenario-based logging usage

[jongpie]

• Resolved Add a way to enforce the usage of scenarios #645 by adding the ability to optionally enforce using scenario-based logging. This is controlled by a new LoggerParameter__mdt record, RequireScenarioUsage, and is disabled (false) by default.
  • When set to false, specifying a scenario is completely optional.
  • When set to true, a scenario is required to be set before any logging can occur. If a logging method is called & the current scenario is null/blank, then Nebula Logger will throw a runtime exception.
• Upgraded LoggerScenarioRecordPage flexipage to use dynamic related lists for Log__c and LogEntry__c
• Added missing field permission for Log__c.TransactionScenario__c to LoggerAdmin permission set

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.06%. Comparing base (11964ad) to head (f8fa572).

❗ Current head f8fa572 differs from pull request most recent head 72eb907. Consider uploading reports for the commit 72eb907 to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #648   +/-   ##
=======================================
  Coverage   95.05%   95.06%           
=======================================
  Files          50       50           
  Lines        5663     5669    +6     
=======================================
+ Hits         5383     5389    +6     
  Misses        280      280           

Flag	Coverage Δ
Apex	95.06% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.