docs: BLA-2526 - Update stickydisk limit from 5 to 10 disks

BLA-2526: This change updates the documentation to reflect the new default limit
of 10 sticky disks per GitHub Action job (increased from 5).

Changes:
- Updated README.md line 29 from 'up to 5 sticky disks' to 'up to 10 sticky disks'

Note: When Docker pull caching is enabled, it reserves one slot, so customers will
effectively have 9 stickydisk slots available in that configuration.

Co-Authored-By: [email protected] <[email protected]>

Author: devin-ai-integration[bot]

README.md

@@ -26,7 +26,7 @@ The sticky disk is formatted as an ext4 filesystem.
   </picture>
 </p>
 
-Blacksmith stores sticky disk artifacts in a secure, highly performant Ceph cluster, running on local NVMe drives. Our runners proxy their requests through our Storage Agents to interact with the Ceph cluster. Each sticky disk is uniquely identified by a key. When a GitHub Action job requests a sticky disk, the last committed snapshot will be cloned and mounted into the runner at the specified path. Once the job completes, the sticky disk will be unmounted and committed for future invocations. At the moment, customers can use up to 5 sticky disks in a single GitHub Action job.
+Blacksmith stores sticky disk artifacts in a secure, highly performant Ceph cluster, running on local NVMe drives. Our runners proxy their requests through our Storage Agents to interact with the Ceph cluster. Each sticky disk is uniquely identified by a key. When a GitHub Action job requests a sticky disk, the last committed snapshot will be cloned and mounted into the runner at the specified path. Once the job completes, the sticky disk will be unmounted and committed for future invocations. At the moment, customers can use up to 10 sticky disks in a single GitHub Action job.
 
 # Use Cases