`foreignApps: [0]` causes simulation call to fail

### Subject of the issue

A developer reported that simulating a transaction that includes a `0` in the foreign apps array causes the simulation to fail. The transaction does not fail when actually submitted.

`foreignApps: [0]` <-- simulate request fails
`foreignApps: [1]` <-- works

### Your environment

JS SDK v3.2

### Steps to reproduce

```ts
// txs is an array of two transactions

const atc = new AtomicTransactionComposer();
const signer = algosdk.makeEmptyTransactionSigner();

for (const txn of txs) {
atc.addTransaction({ txn, signer });
}

const sim = new modelsv2.SimulateRequest({
allowEmptySignatures: true,
allowUnnamedResources: true,
});

const response = await atc.simulate(algodClient, sim);
```

### Expected behaviour

The simulate request should resolve successfully given that the transaction can be submitted successfully. The dev reported the issue did not occur on JS SDK v2.10.0.

### Actual behaviour

The simulate request produces the error `transactionGroup: incomplete group`.