Use gaps of 10 for restore order numbers

Change restore order numbering from consecutive (1, 2, 3...) to gaps
of 10 (10, 20, 30...) to allow easy insertion of new resources without
mass renumbering.

Updated restore orders:
- 1 → 10 (NADs, Secrets, ConfigMaps)
- 2 → 20 (TLS Issuers)
- 3 → 30 (MariaDBDatabase)
- 4 → 40 (MariaDBAccount)
- 5 → 50 (Infrastructure config)
- 6 → 60 (OpenStackControlPlane, Reservation)
- 7 → 70 (RabbitMQ, IPSet)
- 8 → 80 (PVCs, DataPlaneService)
- 9 → 90 (GaleraBackup, DataPlaneNodeSet)
- 10 → 100 (Database restore - manual)
- 11 → 110 (RabbitMQ credentials - manual)
- 12 → 120 (Resume deployment - manual)

Benefits:
- Easy to insert new resources (e.g., order 25 between 20 and 30)
- Up to 9 insertions between any two orders
- No mass renumbering needed
- Common pattern (BASIC line numbers, JCL)

Updated all:
- Restore order table
- CRD annotation mapping tables
- Code examples
- OADP Restore CR examples
- Manual labeling examples
- OpenStackBackupConfig examples
- Controller logic references
- Testing examples

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: stuggi