Generate metric name methods for all metrics

[pkoenig10]

Continuation of #293, but exposing this capability for all metrics.

I think the risk of misuse is minimal. Consumers can always bypass metric-schema entirely if they want. But if they want/need to off-road, it's better to at least have the metrics documented in metric-schema.

There are a couple places in our internal server library where this would be useful.

[changelog-app]

Generate changelog in changelog/@unreleased

What do the change types mean?

• feature: A new feature of the service.
• improvement: An incremental improvement in the functionality or operation of the service.
• fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
• break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
  and external consumers of the service's API (e.g. customer-written software or integrations).
• deprecation: Advertises the intention to remove service functionality without any change to the
  operation of the service itself.
• manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
  performing database surgery, ...) at the time of upgrade for it to succeed.
• migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?

• ❗The break and manual task changelog types will result in a major release!
• 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
• ✨ All others will result in a minor version release.

Type

• Feature
• Improvement
• Fix
• Break
• Deprecation
• Manual task
• Migration

Description

Generate metric name methods for all metrics.

Check the box to generate changelog(s)

• Generate changelog entry

[carterkozak]

I think these should all have been $N because they're name references, shouldn't make much difference in practice outside of cases like this where we pass a *Spec. Up to you if you'd like to replace them here or not.

[pkoenig10]

Oh interesting, $N also supports CharSequence. I assumed it was just for Spec types because the docs say "Use $N to refer to another generated declaration by its name."

[carterkozak]

looks good to me, thanks! Feel free to add merge-when-ready at your convenience

[pkoenig10]

👍

[svc-autorelease]

Released 0.21.0