`runner --cloud-metadata` parsing

From discord#cml/996742882058838057

• doesn’t work: cml runner ... --cloud-metadata "Work Area=TeamName"
• doesn’t work: cml runner ... --cloud-metadata '"Work Area"="TeamName"'
• works: cml runner ... --cloud-metadata '"Work Area"=TeamName'

[dacbd]

Wrote test for these, fix it master via the linked above.

My caveat of the tag parsing may change behavior for users who fangaled the quote/whitespace issues, the example:

cml runner \
  --cloud=aws \
  --cloud-region=x \
  --cloud-metadata="condition one=KeyHasASpace" \
  --cloud-metadata='"condition two"="KeyAndValueAreWrappedWithQuotes"' \
  --cloud-metadata='"condition three"=KeyIsWrappedValueIsNot' \
  --cloud-type=t3.small

results with tags like:

[
  {
    "Key": "\"condition three\"",
    "Value": "KeyIsWrappedValueIsNot"
  },
  {
    "Key": "Id",
    "Value": "iterative-17crj0i6rv6to"
  },
  {
    "Key": "Name",
    "Value": "cml-n467pqly04"
  },
  {
    "Key": "condition one",
    "Value": "KeyHasASpace"
  },
  {
    "Key": "condition two\"",
    "Value": "\"KeyAndValueAreWrappedWithQuotes"
  }
]

@iterative/cml We should warn the discord user before the next release.

[dacbd]

It fixed the original where their workflows stopped working probably after some deps bump. So yes I agree this did break the workarounds which Is why I wanted to make sure we notified the user on discord.

To keep the correct parsing as well as the workaround parsing; I believe this would require upstream changes to yargs parsing so I don’t believe it is feasible to support both.