Bugfix for Name-Shadowing Issues with the Schema Namespace

[jongpie]

Fixed #584 by switching to using fully-qualified Apex class references to several classes in the Schema namespace, like Schema.User, to avoid collision issues in orgs that use name-shadowing classes. These class references are now fully-qualified throughout the codebase

• Schema.Account (these references are only used for tests & sample recipes, not in Nebula Logger's core code)
• Schema.AuthSession
• Schema.LoginHistory
• Schema.Network
• Schema.Organization
• Schema.Profile
• Schema.Topic
• Schema.TopicAssignment
• Schema.User

This is the same concept & approach as the changes made in v4.9.0, v4.9.4, and v4.9.6 to fully-qualify references to classes & enums in the System namespace.

[codecov]

Codecov Report

Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (2735d4e) 95.69% compared to head (e39decd) 95.69%.

❗ Current head e39decd differs from pull request most recent head 278333d. Consider uploading reports for the commit 278333d to get more accurate results

Files	Patch %	Lines
...in/log-management/classes/LogEntryEventHandler.cls	63.63%	4 Missing ⚠️
...logger-engine/classes/LoggerEngineDataSelector.cls	90.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #608   +/-   ##
=======================================
  Coverage   95.69%   95.69%           
=======================================
  Files          48       48           
  Lines        5177     5178    +1     
=======================================
+ Hits         4954     4955    +1     
  Misses        223      223           

Flag	Coverage Δ
Apex	95.69% <90.74%> (+<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.