feat: support sql meta backends and local fs state store backend

[arkbriar]

• Support SQL backends sqlite, mysql and postgresql
• Support local FS state store backend
• Support volumeClaimTemplates and persistentVolumeClaimRetentionPolicy in standalone, meta and compute to persistent local files
• Add examples and test cases.
• Do a release.

After the PR's merged, one can start a pure standalone (1 pod only) with the following command:

helm install -f examples/dev/dev.values.yaml risingwave risingwavelabs/risingwave

The file examples/dev/dev.values.yaml can be found here.

[arkbriar]

Also, if a user just want to try out RisingWave without considering data persistence, the following command shall work on bare k8s.

helm install --set metaStore.sqlite.enabled=true,stateStore.localFs.enabled=true,standalone.enabled=true risingwave risingwavelabs/risingwave

[arkbriar]

Tested with sqlite, PG and MySQL, and RW version v1.7.1.

Conclusions:

• RW works well with PG and sqlite.
• However, RW refused to start with MySQL. It's a bug and I have let @yezizp2012 know.

mismatched types; Rust type `core::option::Option<chrono::naive::datetime::NaiveDateTime>` (as SQL type `DATETIME`) is not compatible with SQL type `TIMESTAMP`

[yezizp2012]

Tested with sqlite, PG and MySQL, and RW version v1.7.1.

Conclusions:

• RW works well with PG and sqlite.
• However, RW refused to start with MySQL. It's a bug and I have let @yezizp2012 know.

mismatched types; Rust type `core::option::Option<chrono::naive::datetime::NaiveDateTime>` (as SQL type `DATETIME`) is not compatible with SQL type `TIMESTAMP`

Opened a PR to fix several issues when using MySQL: risingwavelabs/risingwave#15717. There is only one issue left now, and I am considering how to elegantly solve it.

[yezizp2012]

LGTM! Thx for the job!