fix(maintenance): remove upper peer dependency Middy

[dreamorosi]

Description of your changes

This PR removes the upper bound of the peer dependency on Middy that was introduced in the latest release.

As described in the linked issue, Powertools for AWS (TypeScript) is officially compatible only with Middy 3.x. This is documented both our documentation(see callout titled "A note about Middy") as well as Middy's documentation (here).

This is due to Middy's release cycle that favors more recent Node.js versions, which is not compatible with our current release cycle which instead is aligned with Node.js versions supported by AWS Lambda.

After making the release however, several members of the community have reached out informing us that this new strict peer dependency breaks their builds. While it's possible to circumvent the peer dependency constraint using npm's --force flag, we recognize that this doesn't constitute a good experience and so we are rolling back the change and relaxing the peer dependency constraint.

We'll revisit the topic in our upcoming major release.

Related issues, RFCs

Issue number: #1702

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my change is effective and works
• The PR title follows the conventional commit semantics

Breaking change checklist

Is it a breaking change?: NO

• I have documented the migration process
• I have added, implemented necessary warnings (if it can live side by side)

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication