[core] Add a tag option when interacting with GraphQL endpoints

[saasen]

Type of change (check at least one)

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (fix or update to documentation)
• Maintenance
• Other, please describe:

Does this change require a documentation update? (Check one)

• Yes
• No

Current behavior

The CLI defaults to use the default tag when deploying GraphQL endpoints.

Description

When migrating schemas, it's very useful to specify a custom tag and not break the existing endpoint.

This PR only merges to the gql-tag-option as there's more to do in regards to handle error messages from the GraphQL service.

Note for release

This change makes it possible for developers to provide a custom tag when deploying their GraphQL endpoints. This to either migrating to a new endpoint if the new schema contains breaking changes.

Checklist

• I have read the Contributing Guidelines
• The PR title includes a link to the relevant issue
• The PR title is appropriately formatted: [some-package] PR title (#123)
• The code is linted
• The test suite is passing
• Corresponding changes to the documentation have been made

[rexxars]

👍 Merging into a feature branch