[Bug]: Typescript Burn Interface mismatch

[eike-hass]

Issue description

The Typescript Burn Interface seems to be misaligned. I guess all keys should be optional and nativeTokens should be an optional array as well.

Version

Wasm 1.0.0-alpha.1 and latest develop.

Expected behaviour

Passing Aliases, NFTs, Foundries and native Tokens is optional. It is possible to pass multiple native Tokens.

Actual behaviour

Existence of all keys is enforced and only a single native Token is considered valid.

Can the issue reliably be reproduced?

Yes

Steps to reproduce the issue

this.client.buildAndPostBlock(secretManager, {
    inputs: [aliasInput],
    outputs: [basicOutput],
    burn: {
        aliases: []
    }
});

Errors

Type '{ aliases: never[]; }' is missing the following properties from type 'Burn': nfts, foundries, nativeTokens
Type 'never[]' is missing the following properties from type 'INativeToken': id, amount

Duplicate declaration

• I have searched the issues tracker this issue and there is none

Code of Conduct

• I agree to follow this project's Code of Conduct