docs: add hardware sizing section and remove removed MySQL 8 variables from Requirements.md

[somethingwithproof]

Closes #215
Refs #106

Summary

• Add Hardware Sizing section to Requirements.md with a sizing table covering small (< 500 devices), medium (500-2,000), large (2,000-10,000), and very large (> 10,000) deployments, including guidance on:

  • SSD/NVMe requirement for RRD file directory (spinning disk causes polling backlogs)
  • innodb_doublewrite = OFF only appropriate on SSD
  • Spine CPU threading: 1-2 processes per CPU core
  • Remote data collectors for very large deployments
  • Note on memory vs InnoDB engine for Boost tables on large installs (refs Update documentation - Boost table engine for large Cacti installations #106)

• Remove innodb_additional_mem_pool_size from the description list (removed in MySQL 5.7.4; causes startup failure on any current MySQL or MariaDB)

• Remove innodb_file_format = Barracuda and innodb_large_prefix = 1 from the paste-in config block at the bottom of the file (both removed in MySQL 8.0; cause startup failure)

Test plan

• Verify sizing table numbers are consistent with community guidance
• Verify MySQL 8.0 no longer accepts innodb_additional_mem_pool_size, innodb_file_format, innodb_large_prefix
• Verify config paste-in block still works on MariaDB 10.5+

[Copilot]

Pull request overview

Updates Cacti’s Requirements documentation to add baseline hardware sizing guidance and to remove MySQL/InnoDB configuration variables that are no longer valid on modern MySQL versions.

Changes:

• Added a Hardware Sizing section with a deployment-sizing table and operational notes (SSD/NVMe, Spine scaling, remote collectors).
• Removed innodb_additional_mem_pool_size from the MySQL/MariaDB recommendations list.
• Removed innodb_file_format and innodb_large_prefix from the sample my.cnf paste-in block.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[somethingwithproof]

All three review points are already covered by the current content: the innodb_doublewrite note now spells out the durability trade-off instead of recommending OFF outright, the "Very large" row keeps Disk to pure storage sizing with remote-poller guidance moved to its own note, and the stale PHP 5.4/MySQL 5.6 minimums flagged from #215 are already updated to PHP 8.1 and MySQL 5.7/MariaDB 10.2 elsewhere in Requirements.md. No further changes needed; resolving.

[netniV]

The documentation still lists versions where various options are valid even if by default they are not on later ones.

[TheWitness]

Let's add the autoshink option as well. The innodb_fast_shutdown has to be set to 0 too.

[somethingwithproof]

Rebased onto develop. Floors are now MySQL 8.0 / MariaDB 10.6.28 with 11.8.8 recommended, and the file_format vars are gone.

On autoshrink: it is not a standalone variable, it is an :autoshrink attribute on innodb_data_file_path, off by default, MariaDB 11.2.0+. From 11.2.3 the shrink only runs on slow shutdown, which is why innodb_fast_shutdown = 0 matters. I documented it in the settings list but left it out of the copy-paste my.cnf block, since pasting ibdata1:12M on a server whose ibdata1 is already larger stops it from starting.