Create guidelines on handling CoC violations

Nobody has claimed this yet.

This is a 2-part issue:

1. Handling CoC violations in general
2. Handling CoC violation enforcement requests from the OpenJS Foundation

## Handling CoC violations in general

The Contributor Covenant v2.0 (CCv2.0) provides terse [enforcement guidelines](https://github.com/loopbackio/loopback-governance/blob/f18ebb8c3099597e7a557173801693a18a0221a5/CODE_OF_CONDUCT.md#enforcement-guidelines) which may be difficult to augment into each violation report that the TSC looks into. This can lead to disagreements on how to triage, document and evaluate the impact and severity of the CoC violation.

The CCv2.0 enforcement guidelines were influenced by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity), and we can take influence from Mozilla's other processes as well:

1. [Triage system](https://docs.google.com/document/d/1rQoxKgOBkH1WfC4bDcXq_0y5MK7RWbbeDk4uqNjQMBc/edit#)
Help document the context of the report, such as the background of who is being reported.
2. [Investigation templates](https://github.com/mozilla/inclusion/blob/f887bc3932bb5dc72ee0bd0bda3985266bdb5be4/code-of-conduct-enforcement/investigation/working-group/role-groups.md)
Assist in formally documenting the complaint investigation process, and clearly stating who in the TSC is accountable for pushing the complaint through the process. Aids in providing accountability.
3. [Notification & follow-up communication templates](https://github.com/mozilla/inclusion/tree/f887bc3932bb5dc72ee0bd0bda3985266bdb5be4/code-of-conduct-enforcement/decisions/communication/decision-comms/reported)
Standardises how we communicate with the affected parties.

## Handling CoC violation enforcement requests from the OpenJS Foundation

Although the OpenJS Foundation as the right to request the hosted projects to take action, they have stated that forcing projects to adopt OpenJSF's resolutions are left vague and that historically, CoC violation enforcement were scoped within the project's specific community. See the [OpenJSF CPC Meeting 2022-04-12](https://github.com/openjs-foundation/cross-project-council/issues/864) meeting minutes "Update Contributor Covenant Code of Conduct to v2.1".

Hence, this becomes a more involved process for projects who want to exercise independent evaluation of the report:

1. How much of the report is shown to the hosted projects' CoC contacts?
2. How does the LoopBack TSC evaluate and take action on these reports?
a. Do we also need to perform our own notification and follow-up communications (as above) in addition to what the OpenJSF would do?

The OpenJSF CPC [does not currently provide resources](https://github.com/openjs-foundation/cross-project-council/blob/4e801af388d03edaf370e734fb9e6e6a633ade7e/conduct/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md#resources) for hosted projects to adopt as part of their CoC process.

## Other References

- https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415
- OpenJS Foundation CoC issue: https://github.com/openjs-foundation/cross-project-council/issues/786#issuecomment-900562549
- OpenJSF Foundation CoC requiremens: https://github.com/openjs-foundation/cross-project-council/blob/4e801af388d03edaf370e734fb9e6e6a633ade7e/conduct/FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md

Start with the existing CODE_OF_CONDUCT.md enforcement guidelines and the linked Mozilla investigation and communication references. Review the OpenJS Foundation CPC meeting minutes and FOUNDATION_CODE_OF_CONDUCT_REQUIREMENTS.md for hosted-project expectations. Done means documenting a LoopBack process for triage, investigation, communications, and OpenJS Foundation enforcement requests, including how the TSC evaluates reports.

Written by the indexing model from the issue text.