fix: use identityPool provider directly in auth directive output

[soberm]

Problem

The SchemaProcessor was mapping identityPool to iam when generating auth directive output. This mapping is unnecessary at the schema level since the transform layer already handles it, and it obscures the original provider name in the generated schema.

Issue number, if available:

Changes

• Removed the identityPool → iam provider mapping in SchemaProcessor.calculateAuth()
• Auth directives now preserve identityPool as the provider name in the schema output
• Updated snapshots and integration tests to reflect the corrected provider name

Corresponding docs PR, if applicable:

Validation

• All 36 existing test suites pass (548 tests, 267 snapshots)
• Integration test assertions updated to verify identityPool is preserved in auth directives
• Snapshot files updated to match new output

Checklist

• If this PR includes a functional change to the runtime or type-level behavior of the code, I have added or updated automated test coverage for this change. (see Testing Strategy README)
• If this PR requires a docs update, I have linked to that docs PR above.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

🦋 Changeset detected

Latest commit: f0eb3f0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@aws-amplify/data-schema	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR