Set/update the feature status in the metadata for all features that are not stable

Reference to this issue. Right now, the * is used pretty inconsistently through out the docs. There are some features that have the status set but haven't been updated to the current status or in some cases, experimental/alpha/stable features don't have the status set in the markdown.

E.g: JWT Claim based routing on the feature status page says it is Alpha but the status is set to Experimental Authorization Dry Run says it is Alpha but the status is set to Experimental

Question:

• Do we want to use * to mark all experimental/alpha/beta features or just experimental/alpha or just do not use it at all?

@craigbox @ericvn @howardjohn @kfaseela thoughts?