fix frontend crash on google calendar reminder minutes

[itsababseh]

Summary

• handle numeric enum options correctly in NodeStringInput

Testing

• yarn format
• poetry run format
• yarn type-check
• yarn test (fails: Process from config.webServer exited early)

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	fed631a
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs-dev/deploys/6831fd04dfd28000089cc97c

[deepsource-io]

Here's the code health analysis summary for commits a51af36..fed631a. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success	❗ 3 occurences introduced 🎯 2 occurences resolved	View Check ↗
Python	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[netlify]

✅ Deploy Preview for auto-gpt-docs canceled.

Name	Link
🔨 Latest commit	fed631a
🔍 Latest deploy log	https://app.netlify.com/projects/auto-gpt-docs/deploys/6831fd044451b20008c66732

[AutoGPT-Agent]

Thank you for submitting this fix for the frontend crash with Google Calendar reminder minutes. The implementation looks solid - properly handling numeric enum options by converting them to strings for display and parsing them back to numbers when needed.

To get this PR ready for merging, please address these items:

1. Include the standard PR checklist from our template, as it's required for code changes like this. You can mark sections as not applicable if they don't apply, but the checklist itself should be present.

2. Update the PR title to follow our conventional commit format more precisely by including a scope, such as: fix(frontend): crash on google calendar reminder minutes

3. It would be helpful to provide a bit more context in the description about what was specifically causing the crash with Google Calendar reminder minutes.

4. Regarding the test failure you reported (yarn test failing with 'Process from config.webServer exited early'), please clarify if this is related to your changes or if it's a pre-existing issue with the test environment.