docs: add comprehend doc

[DenovVasil]

Description

add comprehend documentation for issue

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 🤔 Hello! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• docs/components/connectors/out-of-the-box-connectors/amazon-comprehend.md
• docs/components/connectors/out-of-the-box-connectors/available-connectors-overview.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[christinaausley]

Hi @DenovVasil -- do you mind providing a link to the related issue? Just let us know when you are ready for final review from @camunda/tech-writers, and an engineering review.

[DenovVasil]

Hi @DenovVasil -- do you mind providing a link to the related issue? Just let us know when you are ready for final review from @camunda/tech-writers, and an engineering review.

Hi, I added issue link to description
I will ask for your review after I receive approve from dev team.

[akeller]

@DenovVasil are you close to moving this out of draft so we can review and merge? We are prepping to cut the docs and you may need to backport these changes.

[christinaausley]

I have backported this for you @DenovVasil -- may we merge?

[christinaausley]

Note that based on Slack conversation, @DenovVasil is making a few adjustments and planning to merge shortly.

[DenovVasil]

Note that based on Slack conversation, @DenovVasil is making a few adjustments and planning to merge shortly.

I consulted with my team and we decided that version 8.6.0 is not correct it should be 8.7.0

[christinaausley]

Note that based on Slack conversation, @DenovVasil is making a few adjustments and planning to merge shortly.

I consulted with my team and we decided that version 8.6.0 is not correct it should be 8.7.0

Should this go out with the 8.7 release then? If so, please update the labels. @DenovVasil

[christinaausley]

After jumping on a call with @DenovVasil, this can be merged into next, but should be removed from 8.6. Updating this now, and preparing to merge.