Adding Python docs to new template update

[nikomancy]

What?

Updating the Python docs to follow the same multipage pattern as our Javascript docs.

Why?

• The goal is to make the learning journey for engineers working with specific SDKs easier.
• Content is easier to find in the TOC, improving navigability.
• Code samples for typed assignment examples have been added for ease of use.
• Boilerplate prose docs have been added to allow engineers to learn about relevant conceptual information alongside the code without having to context switch to other parts of the docs.

Review instructions

• Let's discuss the Python SDK 4.0 announcement doc. Are there any places in the docs where the differences between 3.0 and 4.0 are different enough that we need to preserve older doc information? Are we safe to get rid of that page?
• Please make sure the code samples are accurate.

Todo before merge

• Delete python.md
• Delete announcing-python-4-0.md
• Update redirects

[netlify]

✅ Deploy Preview for eppo-data-docs ready!

Name	Link
🔨 Latest commit	e07e8ec
🔍 Latest deploy log	https://app.netlify.com/sites/eppo-data-docs/deploys/676495f7f1fd910008ae6302
😎 Deploy Preview	https://deploy-preview-558--eppo-data-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[lukasgoetzweiss]

It looks like this PR drops some of the examples that are currently live. Can we add a page including those? This is a great example of where having a whole python section can help us add dedicated pages for common use cases: batch process jobs, django apps, etc.

Also, can we update this PR to include this feedback from Slack?

[rasendubi]

Review: #561

One of the diffs between pre/post 4.0 is that 4.0 exposes all things from eppo_client directly, whereas pre-4.0 exported things from somewhat random places. (Old locations are still supported but depricated.)