Reconsider Wasmtime's allocation strategy "max table elements" config option

[Stebalien]

We currently use the default of 20k but it sounds like that reserves enough memory for 20k elements up-front even if they aren't used, which is something we should charge for in our memory accounting logic. We currently charge for table use as they're used.