Geo Replicables: Explain technical details of bulk actions in docs

Why are we doing this work

We are working to allow more robust functionality in the bulk actions in Geo and in particular allow customers to fire bulk actions on failing data: Geo: Provide a way to resync and reverify only ... (#263435 - closed)

Currently, our docs do not explain the technical nuances about what a resync/reverify action does in Geo. Additionally, the ideas are a bit scattered around what is and isn't available in the UI vs Rails Console.

Specifically @mkozono shared over on #263435 (comment 431079322) that these technical details are of importance to some customers in understanding what is happening when they are troubleshooting.

I'm realizing that there's a nuance here. The system already resyncs and reverifies failed things. The full description of the ask (for backend) is to reduce the retry count and time back to 0 so that it happens soon rather than up to 1 hour from now. We can't make these kinds of buttons actually do anything right now because it could be many millions of things.

We should update our docs to better explain this.

Relevant links

Implementation plan

  1. Split up sections of Resync and reverify multiple components between UI functionality and Rails functionality

  2. Better categorize actions taken from the Secondary and actions taken from the Primary

  3. Follow a consistent title structure to make it easier to "skim" the headings.

    • Some titles read Resync some read Sync. Align on Resync
    • Remove "one component" language in favor of "ACTION all component resources" as all actions taken are in relation to a singular component.

  4. Explain "how" a resync/reverification works

    • #263435 (comment 431079322)
    • Actions set the retry count back to 0 and a short time in the future
    • These actions don't result in immediate actions but rather re-kicks the queue.
Edited by 🤖 GitLab Bot 🤖