Fix: uncontrolled input in dashboard

[Animesh404]

What kind of change does this PR introduce?

a Bugfix for #889

Summary

• Removed checked property: This avoids conflicting control by letting getInputProps fully manage the checkbox state.
• Added defaultSettings which provides default values for all fields, preventing uncontrolled-to-controlled issues.

Checklist

• My code follows the style guidelines of OpenAdapt
• I have performed a self-review of my code
• If applicable, I have added tests to prove my fix is functional/effective
• I have linted my code locally prior to submission
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (e.g. README.md, requirements.txt)
• New and existing unit tests pass locally with my changes

How can your code be run and tested?

poetry shell
python -m openadapt.entrypoint

[abrichr]

This looks like the third place we are duplicating configuration setting names. Is there any way to populate this dynmamically?

[Animesh404]

we populate this dynamically using config file but sometimes we might get undefined values which might be the reason for warning. So, I added these default values

[abrichr]

Won't this prevent the checkboxes from being checked appropriately depending on the configuration values?

[Animesh404]

...form.getInputProps('RECORD_WINDOW_DATA') this alone should've marked this checked but yes now that I tested it again without checked= property it is not being marked appropriately.

[abrichr]

Closing as part of the architecture transition. The legacy codebase has been moved to legacy/ and frozen at v0.46.0.

If this change is still needed, please:

1. Open a PR against the relevant modular package repository
2. Or re-open this PR targeting the legacy/ directory if it's a critical legacy fix

See PR #960 for details on the new meta-package architecture.