For several functions like: experimental_strftime(), experimental_uuid_v4() and experimental_follower_read_timestamp(), these functions will have to be refactored in applications that are using them when they no longer are experimental. We should think of a different way of introducing experimental functions so they don't have to be refactored in applications.

Update from @rafiss

The product team is coming up with a definition for "alpha" and "beta" features. Once that is established, let's create aliases for all existing experimental functions and settings. (i.e., just make a new name without experimental_ in the name that points to the existing thing.)

Session settings:

• experimental_distsql_planning
• experimental_enable_temp_tables
• experimental_enable_implicit_column_partitioning
• experimental_enable_hash_sharded_indexes
• experimental_enable_unique_without_index_constraints
• experimental_use_new_schema_changer

Cluster settings:

• sql.defaults.experimental_distsql_planning
• sql.spatial.experimental_box2d_comparison_operators.enabled

Functions:

• experimental_uuid_v4
• experimental_strftime
• experimental_strptime

cc @vy-ton

Jira issue: CRDB-3979

Epic CRDB-60948