fix: use dot-delimited type strings for dynamic record and future

[marshacb]

Motivation

The ValueType::DynamicRecord and ValueType::DynamicFuture variants in get_inputs() serialize their type strings with underscores (dynamic_record, dynamic_future) instead of dots (dynamic.record, dynamic.future). This is inconsistent with snarkVM's Display implementation for these types (value_type/parse.rs:71-72).

---

Note

Medium Risk
Changes the serialized type strings returned by Program.getFunctionInputs() for DynamicRecord/DynamicFuture, which may break consumers relying on the previous underscore format.

Overview
Fixes Program.getFunctionInputs() to serialize ValueType::DynamicRecord and ValueType::DynamicFuture using dot-delimited type strings (dynamic.record, dynamic.future) instead of underscore-delimited variants.

This brings the WASM program-introspection output in line with snarkVM’s type string conventions.

^{Written by Cursor Bugbot for commit f7e79a9. This will update automatically on new commits. Configure here.}