docs: integrate playbook into integrate with apify doc

[TC-MO]

restructure the document
expand with technical part of integration playbok
add TODO for OAuth
formatting fixes
style guide fixes

[apify-service-account]

Preview for this PR was built for commit 435034f0 and is ready at https://pr-1608.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit c254f843 and is ready at https://pr-1608.preview.docs.apify.com!

[tomnosek]

A couple of comments from me:

• I'd format the intro to Integration types to bullet points, similarly to how Integrating with Apify has it already. I think italicizing general and Actor-specific isn't sufficient for comfortable reading.
• I'd change the Integrating with Apify heading for something like Getting started or Building integrations because the current heading just repeats the article's name; therefore, it doesn't really distinguish what it'll be about.
• There's one "the Apify Store" and "the Apify Console", where the shouldn't be there. But I believe Dan will catch these.

[TC-MO]

All valid points @tomnosek, just a bit of context for 1.

My train of thought was we introduce the concepts in paragraph with very brief explanations and then they have their own separate paragraphs & headings. I also didn't want to overuse bullet points, while generally they make it easier to read and scan, there already is quite a number of them throughout the whole text.

[apify-service-account]

Preview for this PR was built for commit b6c03974 and is ready at https://pr-1608.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 9b792c15 and is ready at https://pr-1608.preview.docs.apify.com!

[MisaFialova]

Building an integration Actor

The best way to reach out to Apify users is directly within Apify Console.

I don't think this is necessarily the best way to reach out to Apify users and the external integration being the alternative, as we say in the next paraghraph. It makes sense we mention the integration Actor option here - but I wouldn't label it as a best way.

@TC-MO

[MisaFialova]

@TC-MO The only thing I'm missing is mentioning our MCP here. I asked the AI team to provide some info that could be added, but they haven't added it yet, so we can do that in next iteration.

Otherwise you can see my comment's directly int the text and it's good to go from my side.

[apify-service-account]

Preview for this PR was built for commit 4eb1c773 and is ready at https://pr-1608.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 4ff90356 and is ready at https://pr-1608.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 7d8b6f10 and is ready at https://pr-1608.preview.docs.apify.com!

[apify-service-account]

Preview for this PR was built for commit 8e33aa83 and is ready at https://pr-1608.preview.docs.apify.com!