Add support for tag spec v0.3

[sachindshinde]

This PR:

• Adds a tag spec definition for tag spec v0.3.
  • The only change is to add support for the SCHEMA location in the @tag directive definition.
  • This also changes composition to use tag spec v0.3 in output.
• Updates SUPPORTED_FEATURES to include tag v0.3 (which controls supported features during supergraph schema processing).
• Updates the federation spec to use the @tag directive definition of tag spec v0.3.
  • Note this change only uses that directive definition for federation spec v2.3.
  • For federation spec v2.2 and below, we maintain current behavior (which is to use the @tag directive definition of tag spec v0.2).
    • This is arguably a bug, as we should be using the @tag directive definition of tag spec v0.1 for Fed 1 instead of v0.2, but I'm guessing it's benign given no one's complained thus far (and we'd have to run checks if we wanted to change the behavior).
• Updates TagDirective in @apollo/subgraph to use the @tag directive definition of tag spec v0.3.
• Updates tests.

[netlify]

👷 Deploy request for apollo-federation-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	7b88b70

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[pcmanus]

Lgtm. Can you push some changelog entries (in subgraphs-js/CHANGELOG.md and gateway-js/CHANGELOG.md ideally)?

[sachindshinde]

@pcmanus
Sounds good, updated the CHANGELOG.md for subgraph-js and gateway-js (also updated the CHANGELOG.md for composition-js). Will merge into main, let me know if there's anything in the CHANGELOG.md entries I should tweak and I can file follow-up PRs.

[geekmini]

Hi all, I've upgrade form @apollo/subgraph from 2.2.3 to 2.3.1 but found this errors on tags.

"@tag" should have locations field_definition, object, interface, union, argument_definition, scalar, enum, 
enum_value, input_object, input_field_definition, but found (non-subset) field_definition, 
object, interface, union, argument_definition, scalar, enum, enum_value, input_object, 
input_field_definition, schema

It seems this change will breaking existing directives. Is there any guid for migration without breakage that we the community could have a reference to ?

[sachindshinde]

@geekmini Thanks for writing in! Your error looks similar to that reported in #2375 . We've written up some guidance in #2375 (comment) , can you let us know whether that resolves the issue?

[GeekEast]

Hi @sachindshinde yup, upgrade the federation version solves the issue. BTW, I am using Nest.Js as framwork