Add examples for local testing and CI/CD lifecycle management

[Martijn Visser (MartijnVisser)]

Restructures the integration and deployment example around a realistic developer workflow and adds local testing and CI/CD lifecycle management:

• The pipeline logic of Example_08 is now a plugin-free function that is unit tested locally on Apache Flink with mock data from fromValues(), without Confluent Cloud connectivity. The Confluent plugin and the OSS planner both register engine factories under the identifier 'default' and cannot share a runtime classpath, so surefire excludes the plugin and failsafe excludes the OSS planner (documented in the README, including IDE run-configuration setup).
• New integration tests (*IT) run the same pipeline logic against Confluent Cloud on a bounded mock table. They fail fast with a clear message when the required environment variables are missing, so a CI pipeline (e.g. a deploy pipeline with a misconfigured secret) cannot silently skip its verification step and still report success; builds without credentials skip them explicitly with -DskipITs. The required variable names are taken from ConfluentPluginOptions so the check cannot drift from the plugin contract, and a FLINK_PROPERTIES-based configuration is accepted as an alternative. The fixture has a timeout, validates the row threshold was reached, and always stops and deletes its fill statement.
• Example_08's main() is reduced to a deployment entrypoint: configuration via environment variables, a deterministic statement name set through the typed ConfluentPluginOptions.CLIENT_STATEMENT_NAME option, idempotent re-runs, and rejection of stale mode arguments.
• New Example_12_StatementLifecycle performs status/stop/resume/delete on deployed statements by name.
• New CI workflow (format check, compile, local tests, fat JAR; no credentials required) and example deploy/manage workflows under .github/workflows-examples/ for use in downstream projects. The manage workflow passes inputs via quoted environment variables to avoid script injection.
• README gains a developer journey overview, a testing section covering the three test tiers and the Apache Flink (local) limitations, and CI/CD guidance.

Verified: ./mvnw clean verify -DskipITs passes offline (4 unit tests green), verify without credentials fails fast with the expected message, the shaded JAR is unaffected by the test dependencies (no OSS planner classes or service entries), and the integration test has been executed successfully against a live Confluent Cloud environment.

[Timo Theusner (Timm0)]

Can we move this to action inputs? In a real world scenario you will probably want to re-use this action for all applications you might own

[Timo Theusner (Timm0)]

I think we should not include this function here. All of the other examples have no checks whether the given database and catalog are existent and follow the same pattern of having variables for them at the top. Sticking to the same patterns across examples helps a user to focus on the more important parts.