Add name stanza for proper name

[rolandwalker]

Following up on #7673, add a name stanza

• This will obsolete tags :name (before it ever really gets started)
• Documentation will be in a separate PR so that authors don't start using the feature before code release
• Future plan would be to make this mandatory
• Proposed placement in create template is high, which may warrant discussion

There is a bit of hackery needed to expose name in the DSL, because Ruby has already defined a name method. On the backend, this is everywhere referred to as full_name.

Exposing simply name has the virtue of clearly directing all naming activities away from the token, which cannot bear the weight.

[vitorgalvao]

I like the placement, but I’d move it one line down. It’s grouped with url, homepage, and license, i.e. the ones that shouldn’t need much fiddling after the initial setup (considering url has some form of version interpolated, or is always pointing to the latest version). However, for the cases url does need to change, it makes sense to have it higher up; I’ll also use as reasoning that (at least to me) having name and homepage together makes more sense than name and url.

On a tangent note, perhaps we should consider moving appcast higher up, together with version and sha256, since that will also change with every version (because it too has a sha256).

[rolandwalker]

Sure thing. Changed here and in the doc PR.

I'm not ready to move appcast yet. Hopefully the appcast checksums are just a transitional thing we just use to get started (for 99% of cases). What's not yet defined is how appcast will interact with version. That will affect how volatile the appcast stanza may be.

Logically, the appcast doesn't need to be volatile, if the software does the work instead of the Cask author, and I'm trying to get to that.

Also, it's been poorly explained, but I'm purposefully letting the appcast data "cook" for a little while in the real world to gather various cases to develop against.