Queue message value corrupted

[ejizba]

Repro steps

1. Create a storage queue trigger that prints the message content
2. Add a queue message with the content "89e7073266" or "35732122e2" (If you do this in the portal, make sure to check the option to base64 encode)

Expected

It prints the original message content

Actual

It prints "Infinity" or "3573212200"

More info

Turns out this is because we try to JSON.parse the message content and that's what happens when you JSON parse those specific values even if most other strings stay the same. This repros in both v3 and v4, and I don't know what the fix is because it's potentially breaking. Still, this is pretty weird behavior and took me a while to figure out why my I would sometimes have my queue message change causing an e2e test to fail.