Bare Flink cluster deployment mode

The operator is designed to manage a single job. There are use cases where it is desirable to only have the Flink cluster stood up and manually manage the job. For example, during testing I may want to just modify the job jar locally and repeatedly upload to the cluster or use a Flink deployment for experimentation purposes.

Maybe the CRD could have a field that indicates "cluster only" or "user managed" deployment that short circuits the job related state machine?

No files, tests, or entry points are named. Start by tracing the CRD and job-related state machine, then determine how a cluster-only or user-managed mode should be represented and propagated. Done means the operator can create and maintain a Flink cluster without managing its job, with coverage for the new behavior.

Written by the indexing model from the issue text.