chore: remove service spec yarn resolutions

[iliapolo]

These resolutions prevent us from fetching the latest schema. They were added because there are multiple breaking changes in the spec we weren't ready to accept yet.

Are we ready to accept the new spec?

Not quite.

So whats the plan?

We need to remove these resolutions in order to get a service spec update PR that at least surfaces all the breaking changes in order to work on them. So the plan is:

1. Merge this PR.
2. Run the spec update workflow
3. Slap a pr/do-not-merge label on the resulting PR
4. Figure out what to do with the breaking changes it show.
5. Eventually merge the spec update after applying patches or allowing breaking changes to go through.

From a local execution at the time of writing this PR, those breaking changes should be:

├[~] service aws-cognito
│ └ resources
│    └[~]  resource AWS::Cognito::UserPoolDomain
│       └ attributes
│          └[-] Id: string


├[~] service aws-dynamodb
│ └ resources
│    └[~]  resource AWS::DynamoDB::GlobalTable
│       └ properties
│          └[-] PointInTimeRecoverySpecification: PointInTimeRecoverySpecification


│    ├[~]  resource AWS::ECS::Service
│    │  ├ properties
│    │  │  ├ AvailabilityZoneRebalancing: (documentation changed)
│    │  │  └ CapacityProviderStrategy: (documentation changed)
│    │  └ types
│    │     └[~] type ServiceManagedEBSVolumeConfiguration
│    │       └ properties
│    │          └[-] VolumeInitializationRate: integer


│    └[~]  resource AWS::RDS::GlobalCluster
│       ├ properties
│       │  └[-] GlobalEndpoint: GlobalEndpoint
│       └ attributes
│          └[+] GlobalEndpoint: GlobalEndpoint

Wait but you just detailed the breaking changes, can't we just work based of that?

No, we shouldn't be operating on the basis of local executions. The local execution diff is just to get a sense and show that there are indeed a few breaking changes already present.

---

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

[iliapolo]

Adding pr/do-not-merge on this one because there is some coordination needed immediately after and I have to step out for a bit.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.00%. Comparing base (c7a9a3c) to head (713584a).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #33485   +/-   ##
=======================================
  Coverage   81.00%   81.00%           
=======================================
  Files         238      238           
  Lines       14271    14271           
  Branches     2492     2492           
=======================================
  Hits        11560    11560           
  Misses       2425     2425           
  Partials      286      286           

Flag	Coverage Δ
suite.unit	81.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
packages/aws-cdk	79.92% <ø> (ø)
packages/aws-cdk-lib/core	82.16% <ø> (ø)

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 713584a
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.