Ch/clearer anchor flags

[carlhammann]

Changelog

- description: |
    Clearer command line flags for vote, proposal, and constitution anchors
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

On #362, we started a discussion about how the various anchor-related flags could be named in a less confusing manner. This PR implements an idea that we settled upon after a short discussion: Anchors for an x are given by an --x-anchor-url together with one of the following three:

• --x-anchor-metadata for the literal data behind the URL,
• --x-anchor-metadata-file for a file containing the same data, or
• --x-anchor-metadata-hash for the hash of the data.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• The change log section in the PR description has been filled in
• New tests are added if needed and existing tests are updated. These may include:
  • golden tests
  • property tests
  • round trip tests
  • integration tests
    See Running tests for more details
• The version bounds in .cabal files are updated
• CI passes. See note on CI. The following CI checks are required:
  • Code is linted with hlint. See .github/workflows/check-hlint.yml to get the hlint version
  • Code is formatted with stylish-haskell. See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
  • Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7
• Self-reviewed the diff

[Jimbo4350]

LGTM couple of minor changes.