Enable CSIVolumeGroupSnapshot feature gate by default

[xing-yang]

Is your feature request related to a problem?/Why is this needed

Describe the solution you'd like in detail

We moved volume group snapshot to beta while disabled the CSIVolumeGroupSnapshot feature gate by default:
#1194

We can enable it by default in the next release.

Describe alternatives you've considered

Additional context

[pwschuurman]

We can enable it by default in the next release.

Just to confirm, would this be the v9.0.0 release?

[xing-yang]

We are moving this feature to beta while keeping the feature gate disabled by default in the coming release which should be v9.0.0.
So maybe we can make it enabled by default in 9.1.0. (This is TBD)

[xing-yang]

Discussed this in the CSI implementation meeting. We'll cut a 8.2.0 soon (moving to beta while keeping the feature gate disabled by default). Since it is off by default, we don't need to bump the major version. There are RBAC rule changes but those are also not required yet.

When we turn the feature on by default, we'll bump the major version to 9.0.

[yati1998]

@xing-yang the PR for this issue will be created on top of release branch or main?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten