Breaking Changes: reorganize workflows with prefix-based naming and merge duplicates

[clouddrove-ci]

✨ Major reorganization of workflow files and documentation

📝 Prefix Categories Applied:
• terraform- → tf- (9 workflows)
• cloudformation- → cf- (3 workflows)
• pr- prefix for PR-related workflows (auto-assignee, auto-merge, checks, lock, stale, etc.)
• aws- prefix for AWS-specific workflows
• gcp- prefix for GCP-specific workflows
• release- prefix for release workflows
• notify- prefix for notification workflows
• security- prefix for security scanning workflows
• yl- prefix for YAML lint workflows (ymllint → yl-lint)

🔄 Merged Duplicate Workflows:
• Merged tf-checks.yml + tf-tf-checks.yml → tf-checks.yml (with optional version checking)
• Merged tf-workflow.yml + tf-workflow-target.yml → tf-workflow.yml (with optional targeting)

📚 Documentation Updates:
• Removed numbered prefixes from all documentation files
• Updated all workflow references in documentation
• Reorganized README.md alphabetically by prefix category
• Updated all file paths and examples

🎯 Files Renamed:
• 40 workflow files renamed with consistent prefixes
• 32 documentation files renamed and organized
• All references updated throughout repository

✅ Benefits:
• Consistent naming convention across all workflows
• Easier to find workflows by category
• Shorter, more readable file names
• Better organization and maintainability

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting jira issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a Jira issue #123

[pendharevaibhav-cd]

LGTM!