[Security Solution] Removes Detection Rules version bump logic

[spong]

Summary

Resolves #137168 by removing the logic to bump the version of security rules. Also adds an SO migration to set the initial revision as the current version.

Note: this was originally a branched off #147398, so the large commit list is resulting from there as Github doesn't seem to re-write after after a rebase w/ main and a force push.

Checklist

• Documentation was added for features that require explanation or tutorials
  • Found no reference with regards to the auto-incrementing version logic in current docs.
• Unit or functional tests were updated or added to match the most common scenarios

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 1361aa7

Failed CI Steps

• Rules, Alerts and Exceptions ResponseOps Cypress Tests on Security Solution

Test Failures

• [job] [logs] Rules, Alerts and Exceptions ResponseOps Cypress Tests on Security Solution / Bulk editing index patterns of rules with index patterns and rules with a data view Add index patterns to custom rules: one rule is updated, one rule is skipped

Metrics [docs]

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	433	436	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	513	516	+3

History

• 💛 Build #115118 was flaky f8cec53
• 💔 Build #114876 failed 5648323
• 💔 Build #114845 failed d48bec2
• 💔 Build #114794 failed 31257f2
• 💔 Build #114461 failed 426f5e7
• 💔 Build #113481 failed a437c82

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @spong

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[maximpn]

LGTM