Unexpected interactions and behaviour when using default, optional, example input properties

[TinaNikou]

Came across some interactions and behaviours between some input properties that felt a bit unexpected.

1. optional cannot be set to false.What if we wanted to set this dynamically, such as with a ternary based on a value?

const req = input({
    type: "string",
    title: "Required",
    // optional: false // Not possible
});

2. default property cannot be used alongside the optional property.

const opt = input({
    type: "string",
    title: "Optional",
    optional: true
    // default: "Optional default value" // Not possible
});

3. Inputs with default set are always considered optional. When running a board with an input that has a default value in Breadboard-Web, if the board input value is removed and empty, is the default then used anyway or would it allow it to be empty? (This is more theoretical, since currently optional inputs need to be filled in Breadboard Web which has been raised as a separate issue Optional inputs require value in bb-web #2500 )

4. In Breadboard-Web, when the examples is set then the input values default to the first example, rather than being empty. (There is also a separate but related issue to this raised, due to not being able to see or select examples when running the board in bb-web, unless accessing through the schema editor Input examples not displaying as expected in bb-web #2490 )

Any thoughts on these?