docs(maintenance): add versioning and maintenance policy

[heitorlessa]

Description of your changes

Formalize our versioning policy with a dedicated page similar to the AWS SDK, adjusted to Powertools for AWS Lambda (TypeScript) and our community.

Related issues, RFCs

Issue number: #1995

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.

[heitorlessa]

@dreamorosi @am29d ready for review.

Two recommendations after merging tho:

1. Add a documentation banner to emphasize the v2 RFC
2. Update the RFC with the target date for v2

[dreamorosi]

Hi @heitorlessa thank you so much for taking the time to open a PR.

Content looks good and in line with what agreed internally, so we're good on that side.

I've left 2 comments, one of them about a change.

Looking forward to merge this after they're addressed!

[sonarqubecloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

2 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[dreamorosi]

Thank you for this PR, as I said in the other one this will be very useful!