Onboard response ops tasks to use stateSchemaByVersion for task state validation

[mikecote]

Part of #159342.

In this PR, I'm preparing the non-alerting (rule types) response ops task types for serverless by defining an explicit task state schema. This schema is used to validate the task's state before saving but also when reading. In the scenario an older Kibana node runs a task after a newer Kibana node has stored additional task state, the unknown state properties will be dropped. Additionally, this will prompt developers to be aware that adding required fields to the task state is a breaking change that must be handled with care. (see #155764).

For more information on how to use stateSchemaByVersion, see #159048 and https://github.com/elastic/kibana/blob/main/x-pack/plugins/task_manager/README.md.

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[mikecote]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 714f8ae

Metrics [docs]

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	14	16	+2
securitySolution	411	415	+4
total			+6

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	15	17	+2
securitySolution	490	494	+4
total			+6

History

• 💔 Build #142202 failed 5067fce
• 💚 Build #141876 succeeded d6afd7f
• 💚 Build #141742 succeeded 407834d
• 💚 Build #141603 succeeded 52e3a2b
• 💔 Build #141591 failed e3d6601

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

cc @mikecote

[ymao1]

LGTM