Default values for options and array types (frontend)

[aptkingston]

Description

Few changes to default values, and some fixes around schema mutations when editing columns and primary display.

• Adds default value setting for options type (renders a picker instead of a bindable text field, since it needs to be a valid option as the default value)
• Adds default value setting for multi-select type (renders a multi-select picker instead of a bindable text field, since it needs to be a valid option as the default value)
• Ensures that schema properties are consistent upon saving (e.g. required deletes any default value and vice versa)
• Fixes an issue where you could set default value on primary display columns (as the logic for determining whether a field is required or not used an incorrect order of precedence)
• Show default value setting as long as the feature is enabled, but disable it if it cannot be used
• Ensures primary display columns are required and do not have default values when saving
• When changing primary display via the grid, it now also mutates the schema to make the field required and have no default value. Before this, you were able to make any field the primary display column - meaning you could have non-required primary display columns which is not meant to be possible.

Single select:

Multi select:

Addresses:

• https://linear.app/budibase/issue/BUDI-8678/add-the-ability-to-apply-default-values-to-single-and-multi-select