Booleans should not be optional

[petermakeswebsites]

Describe the bug

AFAIK booleans cannot be optional in Pocketbase's SQL, they are either true or false never null or undefined. If this is so, then this output needs to be changed from this:

export type AnimalsRecord = {
	big?: boolean
}

to this:

export type AnimalsRecord = {
	big: boolean
}

to save extra unnecessary type guards.

Versions
pocketbase-typegen version: 1.3.1
pocketbase version: 0.30.2

[patmood]

As mentioned in the PR:

The required field doesn't control whether a value must be explicitly provided. Instead, it controls whether the zero/default value is acceptable.

So we should look at making all fields not optional.

[CKofficial-1797]

Thanks for the clarification!

To keep the scope minimal, would you be open to first fixing boolean fields
to be non-optional, and then discussing whether other field types should
also be generated as required in a follow-up issue?

If that sounds reasonable, I can submit a PR focused only on booleans.