Rework Sidekiq style guide
Over time, our use of Sidekiq becomes complicated. The Sidekiq style guide documentation accumulated with a lot of content, not just a style guide any more. To make it a bit easy to read, we should restructure the document, by breaking it up into smaller pages, each page focuses on a narrow topic.
Proposal
@smcgivern proposed a new structure in &596 (comment 796527208).
- A landing / index page with the basics (ApplicationWorker, retries, queues, tests, arguments logging, job payload size, the map you're adding) and links to the other pages.
- Separate pages for:
- Compatibility across updates.
- Job attributes - urgency, resource boundaries, external dependencies, feature categories.
- Idempotency / deduplication.
- Data consistency / load balancing.
- Limited capacity.
- Worker contexts (maybe this should just be a logging page and have arguments logging too?).
- Each of queue namespaces, versioning, and weights can probably go on its own page with a note that we don't really use those features much, or we could put them on the main page - I'm not 100% sure.