Consistent HUB_STACK_NAME parameter support

[oginskis]

The HUB_STACK_NAME parameter is a de-facto human-readable stack identifier generated when a new stack gets initialized with the hubctl stack init extension. It should appear in the state even if a user does not explicitly add it as a stack parameter, otherwise, it causes several technical issues (for example, it's not possible to recover the stack from its remote state).

During the hubctl verb command, the HUB_STACK_NAME should be handled as follows:

• if the hub state already exists, try to find hub.stackName in the stack parameters
• if found: use the existing value
• if not found OR existing hub state is not provided: use the value from the HUB_STACK_NAME environment variable AND add it to the state as hub.stackName
• if the HUB_STACK_NAME environment variable is not set: generate a new value using petname library AND add it to the state as hub.stackName

[akranga]

@oginskis any progress?

[oginskis]

This is done and released. Moved to done.

[oginskis]

Sorry, not yet released, will go to 1.0.14

[oginskis]

Released in v1.0.14