Recently we have been getting a lot of support cases involving Quay GC behavior. Some of these has stemmed from a confusion how GC is supposed to operate.  Our current documentation does not provide any explanation of the GC expected behavior beyond simple descriptions on the GC parameters in the config schema.

Task is to add a new section focused on documenting the expected GC behavior (perhaps a chapter within "Manage Quay").

Some suggested topics:

• What is GC, why does Quay provide a GC behavior?
• How to and why you would use GC.
• How GC relates to Quota Limits (post 3.7)
• Implications of turning off GC (things don't get deleted immediately, they just hang around)
• Deeper dive into each specific GC function
  • Namespace GC
  • Repository GC
  • Tag GC
• How to detect that GC is working correctly- and ways to 'measure' the storage reclamation

A review of the linked cases will also help identify critical information our customers might need.