fix: ComponentVariableYAML.Proto panics on unconvertible value, aborting the whole project parse

[nishantmonu51]

• ComponentVariableYAML.Proto() panicked when a component or canvas input variable had a value: that structpb.NewValue cannot convert. Since there is no recover() in the parser, a single bad value: in one file aborted the entire project parse.
• The most likely trigger is a bare date default like value: 2024-01-01, which yaml.v3 decodes into a time.Time.
• The value is now converted with pbutil.ToValue, which handles time.Time (and other YAML-decoded types), so date defaults now work. Any remaining conversion error is returned as a normal parse error scoped to the file.
• Added a regression test (TestComponentInputDateValue) covering the panic trigger.

Manual testing steps:

1. Start Rill Developer (rill start) on any working project.
2. Create components/panic-test.yaml with:

   type: component
   markdown:
     content: "hello"
   input:
     - name: start
       value: 2024-01-01

3. Before this fix: the whole project parse fails; every dashboard and model becomes unavailable, and the runtime logs show a recovered panic with invalid type: time.Time from the ProjectParser reconcile.
4. After this fix: the component parses successfully, with the date default normalized to the string 2024-01-01T00:00:00Z; all other resources keep working.

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated. If so, create a separate Linear DOCS issue
• Intend to cherry-pick into the release branch
• I'm proud of this work!

[nishantmonu51]

@codex: review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 3bf1665653

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".