Add numeric outputs to AnswerUnit

[oco777]

Summary

• add shared answer retrieval logic and reuse it for string, float, and int outputs
• expose new numeric AnswerUnit ports with float parsing and rounded int conversion while keeping the existing string port
• document the expanded AnswerUnit outputs in VS_Scratch_Mapping

Testing

• Not run (not requested)

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ 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".

[chatgpt-codex-connector]

Avoid locale-dependent answer numeric parsing

GetAnswerFloat relies on float.TryParse with the current culture, so on locales with comma decimal separators (e.g. de-DE/fr-FR) entering a Scratch-style decimal like 1.5 produces answerFloat/answerInt as 0 and comma input 1,5 is parsed as 1.5 even though Scratch treats comma-separated input as text. Numeric answer ports should parse with culture-invariant rules to keep results consistent with Scratch regardless of OS locale.

Useful? React with 👍 / 👎.