SF-2392 Add event metric logging

[pmachapman]

This PR adds support for logging events via the [LogEventMetric] attribute.

To access it, a button is added to the serval admin page. Although permissions are granted for project admins to view the event log, a link is not provided in the UI until we are ready to expose it to a wider audience.

This PR is intended to be a minimal MVP leaving enough scope for us to expand in the coming months. Perhaps the bulk of the new code is unit tests for existing functionality that did not have unit tests.

See https://github.com/sillsdev/web-xforge/wiki/Event-Metric-Logging for documentation on how this feature works and how to use it.

---

This change is 

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.97%. Comparing base (450be10) to head (b8749b7).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2894      +/-   ##
==========================================
+ Coverage   80.89%   81.97%   +1.08%     
==========================================
  Files         533      545      +12     
  Lines       31262    31536     +274     
  Branches     5083     5112      +29     
==========================================
+ Hits        25288    25851     +563     
+ Misses       5211     4939     -272     
+ Partials      763      746      -17     

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

[kylebuss]

I'm not certain that both the event-metrics.component and event-metrics-log.component are necessary. Is there a reason for two separate components for this?

Reviewed 5 of 11 files at r1, 5 of 10 files at r2, 8 of 11 files at r3, 2 of 8 files at r4, 17 of 21 files at r6, all commit messages.
Reviewable status: 37 of 41 files reviewed, 9 unresolved discussions (waiting on @Github-advanced-security[bot] and @pmachapman)

---

src/SIL.XForge.Scripture/ClientApp/src/app/event-metrics/event-metrics-log.component.ts line 35 at r6 (raw file):

  constructor(
    noticeService: NoticeService,
    private readonly i18n: I18nService,

Will this be needed since it's an admin only screen?

Code quote:

private readonly i18n: I18nService,

---

src/SIL.XForge/EventMetrics/EventScope.cs line 1 at r6 (raw file):

namespace SIL.XForge.EventMetrics;

Should we consider adding Users scope? For SF invites and roles?

[pmachapman]

I'm not certain that both the event-metrics.component and event-metrics-log.component are necessary. Is there a reason for two separate components for this?

This PR is still work in progress. I am still writing this (and other) areas of the code.

Dismissed @Github-advanced-security[bot] from 7 discussions.
Reviewable status: 37 of 41 files reviewed, 2 unresolved discussions (waiting on @Github-advanced-security[bot] and @kylebuss)

---

src/SIL.XForge/EventMetrics/EventScope.cs line 1 at r6 (raw file):

Previously, kylebuss (Kyle Buss) wrote…

Should we consider adding Users scope? For SF invites and roles?

These can be added if needed.

---

src/SIL.XForge.Scripture/ClientApp/src/app/event-metrics/event-metrics-log.component.ts line 35 at r6 (raw file):

Previously, kylebuss (Kyle Buss) wrote…

Will this be needed since it's an admin only screen?

Yes, as project admins will access it.

[kylebuss]

src/SIL.XForge/EventMetrics/EventScope.cs line 1 at r6 (raw file):

Previously, pmachapman (Peter Chapman) wrote…

These can be added if needed.

nit Can the EventScope be renamed to AppComponent or AppFeature? I think this would be useful for the Help Videos and would like to use the enum.

[kylebuss]

Reviewed 6 of 6 files at r17, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @pmachapman)

[kylebuss]

Reviewed 2 of 3 files at r18, 6 of 6 files at r19, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @pmachapman)