docs(build_recipes): add initial build recipes structure

[leandrodamascena]

Issue number: closes #7162

Summary

This PR creates the initial structure to add the build recipes documentation to help developers package Lambda functions with Powertools for AWS Lambda (Python) using different build tools and dependency managers.

Changes

New documentation structure:

• docs/build_recipes/index.md - Overview, terminology, and navigation guide
• docs/build_recipes/getting-started.md - Prerequisites and tool selection guidance
• docs/build_recipes/cross-platform.md - Architecture compatibility, GLIBC considerations, and Python wheels
• docs/build_recipes/build-with-{tool}.md - Dedicated guides for pip, Poetry, uv, SAM, CDK, and Pants
• docs/build_recipes/performance-optimization.md - Cold start and package size optimization
• docs/build_recipes/cicd-integration.md - GitHub Actions and CodeBuild examples
• docs/build_recipes/troubleshooting.md - Common issues and solutions

User experience

Before:

• No dedicated build recipes documentation
• Developers had to figure out packaging approaches on their own
• Common issues with cross-platform builds and GLIBC compatibility
• No guidance on choosing between different build tools

After:

• Clear, navigable documentation for all major Python build tools
• Step-by-step recipes with working examples
• Proactive guidance on avoiding common deployment pitfalls
• Easy tool selection based on project requirements
• Comprehensive troubleshooting section for quick issue resolution

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

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.

[leandrodamascena]

Hey @dreamorosi I need a review here, pls.

[dreamorosi]

Thanks looks good.

Please let's address all the MKDocs build warnings when you can - a few of them are related to pages you're linking here which are not present yet (expected) but there are also many others for dead links in pages.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud