[DOCS]: Update docs to contain information about access permission needs for each resource/data source

[deiga]

Describe the need

We constantly get questions or issues regarding missing permissions to some resources. The provider docs should include information of permissions necessary for each resource.

Maybe we even should add a section to the Issue template asking for Auth mode and permissions granted.

This is a fairly large effort as we need to update almost all docs.

SDK Version

No response

API Version

No response

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[stevehipwell]

@deiga we could start by adding links to the API calls used which "should" provide the required permissions and will allow us to evaluate which resources should be considered for splitting up.

I think we could add a couple of PR checkboxes such as "I've run the tests for the modified resources locally." (with input for console output) & "I've updated the documentation to match provided pattern." (where the pattern has a requirement to list the used APIs).

[deiga]

@deiga we could start by adding links to the API calls used which "should" provide the required permissions and will allow us to evaluate which resources should be considered for splitting up.

I think we could add a couple of PR checkboxes such as "I've run the tests for the modified resources locally." (with input for console output) & "I've updated the documentation to match provided pattern." (where the pattern has a requirement to list the used APIs).

@stevehipwell Love this idea!