docs(ootbc): deprecate power Automate Connector

[Oleksiivanov]

Description

deprecate power Automate Connector

https://github.com/camunda/team-connectors/issues/617

When should this change go live?

TBD

• This change is not yet live and should not be merged until {ADD_DATE} (apply hold label or convert to draft PR)?
• There is no urgency with this change.
• This change or page is part of a marketing blog, conference talk, or something else on a schedule.
• This functionality is already available but undocumented.
• This is a bug fix or security concern.

PR Checklist

• I have added changes to the relevant /versioned_docs directory
• I have added changes to the main /docs directory (aka /next/), and I've assigned an engineering manager or tech lead as a reviewer, or my changes do not require an Engineering review.
• My changes require a technical writer review, and I've assigned @christinaausley as a reviewer,

[github-actions]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[christinaausley]

@pepopowitz @akeller In a case like this, how would you like me to handle redirects? I ask because we haven't gotten around to https://github.com/camunda/developer-experience/issues/151 yet. I can add a redirect to the Connectors overview page, but should I make this change in next as well, or only in our versioned docs and track this via a method @akeller outlined in this issue?

[akeller]

@christinaausley make the change in /next/ as well. 100% agree with redirecting to the overview page.

[pepopowitz]

Re: redirects -- if the redirect is also made in vCurrent/older versions, then a future version release will already have the move accounted for and I won't need to create new redirect rules. From that perspective, it doesn't matter what you do in vNext.

Based on this I will add some clarity to https://github.com/camunda/developer-experience/issues/151, because it doesn't call out that the only moves that are hard to track are the ones that only happen in vNext.

[Oleksiivanov]

@christinaausley , can I merge this PR, or should I wait for to someone review it?