Incorrect YAML generated

- getApiV1BoxesUnspentByaddressP1 (api/v1/boxes/unspent/byAddress/{p1})
- The `items` field has time List[TransactionInfo] in yaml, but not in the actual output.

- OutputInfo
- AdditionalRegisters is declared as `type: object` in the generated yaml, which is represented as HashMap[String, String]. However the method returns an object for each register value and the type of that object is not declared in yaml.
```
"additionalRegisters": {
"R4": {
"serializedValue": "0702472963123ce32c057907c7a7268bc09f45d9ca57819d3327b9e7497d7b1cc347",
"sigmaType": "SGroupElement",
"renderedValue": "02472963123ce32c057907c7a7268bc09f45d9ca57819d3327b9e7497d7b1cc347"
},
"R5": {
"serializedValue": "07033fc3f2fb852242405e4977ee3b1ce7e38710cb27389f4ba461b6b8fdc411d8aa",
"sigmaType": "SGroupElement",
"renderedValue": "033fc3f2fb852242405e4977ee3b1ce7e38710cb27389f4ba461b6b8fdc411d8aa"
}
},
```

- duplicated types declared in yaml: OutputInfo and OutputInfo1, InputInfo and InputInfo1, TransactionInfo and TransactionInfo1
-

Start at the getApiV1BoxesUnspentByaddressP1 endpoint and inspect the generated YAML for items, OutputInfo, InputInfo, and TransactionInfo. Compare the declared schemas with the example output, then verify that the list type, AdditionalRegisters value object, and duplicate type declarations are corrected.

Written by the indexing model from the issue text.