Promoting kind beta feature coverage to release blocking

[BenTheElder]

x-ref #2888 for the split between "enabled" (just toggles the gate and runs GA tests) and "features" (runs tests that actually intentionally use the features)

We have had stable coverage for many releases now of kind with beta features enabled and beta tests running, we have improved the ability to tag tests associated with beta features in kubernetes/kubernetes#131040

We currently have https://testgrid.k8s.io/sig-release-master-blocking#gce-cos-master-alpha-features so there's clear precedent for release blocking signal of non-GA features .. we still don't want to release totally broken features to users. But there is currently a gap in non-default beta features (typically a beta feature associated with a beta API) in the release blocking signal.

I propose we close this gap by promoting the kind-beta-features job to release-blocking

https://testgrid.k8s.io/sig-release-master-informing#kind-master-beta-features

@aojea @pohly and I have been monitoring these jobs, there is a lot more detail on the jobs outlined in #2888 which proposes updating the release informing set with respect to alpha/beta features.

This particular job should already meet the bar for release-blocking and we have no major changes planned for it.

See also: kubernetes/enhancements#5242

[BenTheElder]

/kind feature
/sig release

[pohly]

+1 from me.

[BenTheElder]

cc @kubernetes/sig-release-leads @drewhagen @tico88612

[BenTheElder]

Filed the PR: kubernetes/test-infra#35796