Add binary module upload support and code size/limit informational output

[shanemadden]

• Adds support for .wasm binary file upload - now ignoring files other than .js/.wasm (instead of avoiding stripping their file extension then uploading them as utf-8 text) and logging that it does so, as I don't think there's use cases that would need that, but correct me if I'm wrong!
• Tracks and adds some log output showing the size of the code upload and the percentage of the code upload limit being used.

[AlinaNova21]

now ignoring files other than .js/.wasm (instead of avoiding stripping their file extension then uploading them as utf-8 text) and logging that it does so, as I don't think there's use cases that would need that, but correct me if I'm wrong!

I've actually had use cases for that before, uploading raw json or other encoded formats, not using it currently, but have before.

[shanemadden]

Gotcha - so then for those, I'm thinking leave the extension as-is, encode as utf-8 - and maybe print a bit of text that says that binary data might be lost? 🤔 (essentially, the old behavior with more logging)

[shanemadden]

Updated implementation to just do what it used to for other file types, with a bit of added logging. (There might be other file formats people would also want to upload as binary for loading from their bots, so the logging makes clear that it's uploading 'as text' - not going to try to predict what file extensions they'd want but will serve as a hint for what they need to change to get it uploading those as binary)

[CarsonBurke]

@AlinaNova21