docs(batch): extract and fix examples

[michaelbrewer]

Issue number:

• Split from: Docs: Move code snippets into dedicated python files add formatting and linting, fixing any outstanding errors #1064
• Original pr: fix(docs): extract code snippets into dedicated python files and fix examples #1065
• Fixes: Docs: Batch - Pydantic integration examples #1208
• Fixes: Docs: Batch - creating a custom batch processor example has python syntax errors #1209
• Fixes: Docs: Batch - Testing your code examples has syntax errors #1211

Summary

Extract code examples from the batch documentation

Changes

Please provide a summary of what's being changed

Changes:

• Extract examples for batch
• Fix python syntax and missing imports
• Fix yaml syntax
• Add make tasks to format, compile and lint examples to prevent future errors
• Update or correct line highlights

Bug fixes in this PR:

• Fix examples in Batch - Pydantic integration ( See issue Docs: Batch - Pydantic integration examples #1208 )
• Fix missing parameter in success_handler Batch - Creating a custom batch processor example ( See issue Docs: Batch - creating a custom batch processor example has python syntax errors #1209 )
• Fix python syntax errors (Missing closing quote ["]) in Batch -Testing your code examples ( See issue Docs: Batch - Testing your code examples has syntax errors #1211 )
• Fix missing imports in Batch - Extending failure handling mechanism in BatchProcessor example
• Fix import for Batch - Customizing boto configuration example
• Clean up Batch - Accessing processed messages via context manager example removing unused imports and fix line highlights.

User experience

Please share what the user experience looks like before and after this change

Code examples can now be used without syntax errors

Hosted version is here: https://gyft.github.io/aws-lambda-powertools-python/latest/

Checklist

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

• Meet tenets criteria
• I have performed a self-review of my this change
• Changes are 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.

[codecov-commenter]

Codecov Report

Merging #1114 (f960235) into develop (9d8dd1b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1114   +/-   ##
========================================
  Coverage    99.88%   99.88%           
========================================
  Files          119      119           
  Lines         5423     5423           
  Branches       618      618           
========================================
  Hits          5417     5417           
  Misses           2        2           
  Partials         4        4           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d8dd1b...f960235. Read the comment docs.