add instructions for requesting Confluence edit access + improve requirement expectations

[mollycule]

Added

• instructions for requesting Confluence edit access

Changed

• make an explicit required actions section
• make affinity groups optional, not required for ACCESS Documentation badge
• action item for news/events should be review submission instructions, not active submissions

[mollycule]

Please see https://readthedocs-access-ci-org--104.org.readthedocs.build/projects/integration-roadmaps/en/104/tasks/Knowledge_Base_v2.html for the proposed changes

[jpnavarro]

ACCESS Resource Description is required badge and a prerequisite to this badge, so these instructions should not repeat CiDeR instructions that are/should be in the ACCESS Resource Description badge.

ACCESS Affinity Group is a separate badge with its own instructions. Need to move and merge these affinity group instructions with that badge.

@vg40506 , what does the following paragraph mean? "ACCESS projects, integrated resources, and central service operators may also request integration with the following Knowledge Base services".

RP instructions need to first and primarily clearly outline actions that RPs need to take, and second, inform them what ACCESS will do, and clearly separate the TODOs from the SO YOU KNOW information.

[mollycule]

ACCESS Resource Description is required badge and a prerequisite to this badge, so these instructions should not repeat CiDeR instructions that are/should be in the ACCESS Resource Description badge.

ACCESS Affinity Group is a separate badge with its own instructions. Need to move and merge these affinity group instructions with that badge.

Agreed. I was trying to keep the scope small for this PR to primarily get the steps on how to get Confluence edit access published because it's been a requested RP improvement.

I think that the removal of the CiDeR and ACCESS Affinity Group content would be good as a separate PR that I'm happy to create preferably after this PR is merged.

@vg40506 , what does the following paragraph mean? "ACCESS projects, integrated resources, and central service operators may also request integration with the following Knowledge Base services".

RP instructions need to first and primarily clearly outline actions that RPs need to take, and second, inform them what ACCESS will do, and clearly separate the TODOs from the SO YOU KNOW information.

That's the goal I had for the "Required Actions" section. I'm not entirely sure how the ACCESS Support team wants the content to look, and I think we can help improve the docs with multiple separate PRs that address specific aspects.

@jpnavarro, are you okay with me keeping the scope of this PR to be adding instructions for Confluence edit access + making the required actions a bit more prominent, and then creating a separate PR for the CiDeR/Affinity content removal?

Afterwards, I think it'd be good to meet with the ACCESS Support team to discuss the goals/future of the "Knowledge Base Service Integrations" section.