Serialization mismatches break DSA_PrivateToPublic and KDF_SRTP/SRTCP structured inputs

DSA_PrivateToPublic::Serialize only writes priv, but the generator emits p/g/priv and the wolfCrypt module expects p/g. Structured mutator also parses p/g/priv, so the fields get lost and the module receives empty/invalid p/g.
KDF_SRTP/KDF_SRTCP::Serialize do not write index, yet the generator fills it and the wolfCrypt implementations consume it. Structured mutator previously read the field, but it’s missing in the payload, causing misalignment and fallback to byte-level mutation.
Impact:

Structured mutations for these operations mostly fail or degrade to byte-level mutation.
Backends cannot use full parameters; coverage drops and OutOfData may occur.
Suggested fixes:

In DSA_PrivateToPublic::Serialize, serialize g, p, and priv in the same order as the generator/mutator.
In KDF_SRTP and KDF_SRTCP::Serialize, serialize index along with key/salt/kdr/key1-3Size.

Locate DSA_PrivateToPublic::Serialize and the KDF_SRTP/KDF_SRTCP Serialize methods, then compare their field order with the generator and structured mutator paths described in the issue. Confirm that g, p, priv, and index survive structured serialization and that the affected operations no longer receive empty parameters or fall back to byte-level mutation.