[Integrations docs] Add permissions set for specific input types

[alaudazzi]

As a follow-up on #11603 and #6771, this issue proposes to provide more granular information where needed, and consolidate similar settings for the various input types. A few points to consider:

• the integrations that use the same input (for ex. all integrations that use AWS S3) should refer to the same permission set
• locate the permissions set in one place to facilitate content standardization and maintenance
• engage with integrations devs & doc team as this effort might require some sort of include/import docs in each integration
• this doc enhancement affects both the O11y and the Security organization

[lucabelluccini]

Ideally, this should be done per datastream and not per integration.
Each data stream can have a different input and therefore different requirements/permissions.

Example with AWS Integration.
It contains a huge amount of data streams / sub-integrations.
Some of them rely on aws-s3 input (polling or SQS), others on aws-cloudwatch input, other httpjson (e.g. CloudTrail logs from third party REST API). For each one, there's a separate set of requirements and credentials.

[alaudazzi]

CC @haetamoudi