agoricNames: managing naming consistency between dApps and chain

[dckc]

What is the Problem Being Solved?

In #4026, we're renaming 'autoswap' to 'amm' in agoricNames in the treasury package. The code uses plain string literals, which suggests it's an arbitrary choice, but it's actually constrained by expectations from the dApp front-end.

Description of the Design

Perhaps factor out the string constants into a new package?

The java ecosystem seems to use API jar files for this sort of thing:

• java - What's the purpose: api.jar + impl.jar + bundle.jar? - Stack Overflow

Or perhaps triangulate via documentation?

Security Considerations

I can't think of any.

Test Plan

Existing tests are likely to establish that this is working.

cc @Chris-Hibbert @michaelfig

[Tartuffo]

@dckc Can you please put an estimate on this one?

[dckc]

I estimate 1 to triangulate via documentation (which @dtribble made supportive noises about).