Improve script confirmer handling and definition parser support; enhance error diagnostics and clean generated parser sources

[bennert]

Summary

This PR consolidates the latest changes around script confirmer handling and definition file parsing.
It also improves diagnostics when loading definitions fails and cleans up generated parser sources.

Changes

1. Fixed script parser confirmer interaction handling.
2. Extended the definition parser to accept unquoted INFO(...) as STRING condition text.
3. Updated definition lexer/parser to support the new .def syntax.
4. Removed generated parser source files from Source libraries to reduce duplication and noise.
5. Included full exception details when definition loading fails.

Why

1. Improve robustness and predictability of script/confirm interactions.
2. Support the intended newer definition syntax.
3. Make troubleshooting easier with richer error details.
4. Keep the codebase cleaner and easier to maintain by removing generated artifacts.

Impact

1. Parser behavior changes may affect existing definition/script files.
2. No broader functional regression is expected outside parsing/confirm flows, but additional validation on existing scripts is recommended.

Validation

1. Build and smoke-test relevant projects.
2. Validate parser behavior on representative .def files (including unquoted INFO(...)).
3. Test script flows involving confirmer interactions.
4. Verify negative path: definition load failures now surface full exception details.