fix(omnigraph): make @transport repeatable

[ardatan]

When using bare merging which is basically regular schema merging compared to stitching, @transport directive can exist on schema multiple times.
And this makes the merged schema invalid so @transport needs to be repeatable.

[github-actions]

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
@graphql-mesh/json-schema	0.101.3-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎
@graphql-mesh/mysql	0.99.2-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎
@graphql-mesh/openapi	0.101.3-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎
@graphql-mesh/raml	0.101.3-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎
@omnigraph/json-schema	0.101.3-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎
@omnigraph/mysql	0.3.2-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎
@omnigraph/openapi	0.101.3-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎
@omnigraph/raml	0.101.3-alpha-20240702134651-a52b3aca37d7e320b11871aad4c0f668cebed4ae	npm ↗︎ unpkg ↗︎

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://baea5865.graphql-mesh.pages.dev

[dr3]

Thanks for the speedy fix! LGTM locally, correctly see

directive @transport(subgraph: String, kind: String, location: String, headers: [[String]], queryStringOptions: ObjMap, queryParams: [[String]]) repeatable on SCHEMA

in my schema and graphql validate is happy