Proposal: Add a new "meetings" component for initiative (and other?) meetings.

Problem/Motivation

A few initiatives (e.g. https://www.drupal.org/project/cmi2 and https://www.drupal.org/project/jsdrupal and layouts (not sure the URL) have started doing this AWESOME thing borrowed from the Drupal Diversity & Inclusion initiative, of creating issues for each one of their meetings. This serves the double purpose of documenting what the meeting was about, and giving issue credit to the folks who participated. Example: https://www.drupal.org/project/jsdrupal/issues/2973337 AWESOME.

Except:

1) You need to know the magic project page URLs to find these meeting minute issues (which limits their visibility to hardcore insiders only, basically.)
2) The credit shows up as—for example—"Drupal core - JavaScript Modernization Initiative" rather than what it actually is, which is some major aspect of "Drupal core" (this is also more "prestigious" as issue credit goes).

Proposed resolution

To address both of these problems, add a "meetings" component that these meeting minute issues can be filed against instead.

Pros:
1) Promotes this approach to documenting/crediting meetings as a general best practice.
2) Allows bringing up a list of all the meeting minutes across initiatives with a simple search, for improved transparency.
3) Provide more accurate credit to those pushing forward the most important issues in Drupal.

Cons:
- Are there any?

Remaining tasks

We would need something like #2810485: Allow more maintainers to grant credit to enact this, so anyone with "Maintain issues" permission (as opposed to "Write VCS") could credit others on issues. And this has other benefits as well, such as cutting down commit time.

Maybe also come up with a standard title template for these meeting issues to follow (e.g. "[$initiative Meeting] YYYY/MM/DD")

User interface changes

A new component in the SEA of components. So, minimal.

API changes

None.

Data model changes

None.