CRD schema required for object validation in newer Kubernetes releases

Nobody has claimed this yet.

Newer versions of Kubernetes (e.g. 1.20+) perform type-validation of data written to the CRD. The CRD for the Flink operator currently does not define a schema for the `status` object. This leads to Flink applications never advancing in the state machine, as their updated state cannot be written.

This leads to logs like the following, where the app never advances beyond the `CreatingCluster` state:
```
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Handling state for application","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Jobmanager service already exists","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Logged Normal event: CreatingCluster: Creating Flink cluster for deploy b6178add","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Handling state for application","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Jobmanager deployment already exists","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Jobmanager service already exists","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Versioned Jobmanager service already exists","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Taskmanager deployment already exists","ts":"2022-03-11T04:21:38Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Handling state for application","ts":"2022-03-11T04:22:07Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Jobmanager deployment already exists","ts":"2022-03-11T04:22:07Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Jobmanager service already exists","ts":"2022-03-11T04:22:07Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Versioned Jobmanager service already exists","ts":"2022-03-11T04:22:07Z"}
{"json":{"app_name":"flink-test-app","ns":"aws-us-east-1-dos1","phase":""},"level":"info","msg":"Taskmanager deployment already exists","ts":"2022-03-11T04:22:07Z"}
```

Locate the Flink operator's CRD definition and inspect how the status object is represented. Reproduce the issue on a Kubernetes release with CRD type validation enabled, then verify that status updates are accepted and applications advance beyond CreatingCluster.

Written by the indexing model from the issue text.