Allow attaching common filetypes to POST requests

[Nutcake]

Is your feature request related to a problem? Please describe.

Currently there is no good way to extract a lot of content that can be generated in engine (images, audioclips) to external services in an automated fashion (ie with ProtoFlux). Doing this can be desireable in cases where this data needs to be processed in a way that's either too computationally expensive or too algorithmically complex to reasonably be done in-engine.

Take for example the popular SSTV system, which needs to upload captured image files to a third-party API to function. It does this by iterating over the pixels of the image one by one and encoding them to RGB-Hex values that get concatenated to a huge string which then gets attached to a POST request.

This approach is cumbersome, unneccesarily expensive and only makes sense for the small image-sizes required by that system. Additionally there is no known similar approach for audio files.

Describe the solution you'd like

Add additional ProtoFlux nodes which allow attaching the following data-types as a POST request body:

• Image textures with additional encoding selection input (jpeg, webp, etc),
• Audio clips with additional encoding selection input (ogg, wav, etc).
• Slot hierarchies. Takes a slot as input and sends the slot and all children, their components and values as json/bson
• Possibly mesh-data? Though I see little reason to do that for know.

This functionality could additionally be extended to websockets.

Describe alternatives you've considered

The alternative is to convert the desired data to a string manually and send that with the POST String node, however:

• Images can be encoded manually pixel by pixel as explained above but this process is suboptimal.
• As far as I know audio cannot be encoded at all since there is no way to access the raw audio data in ProtoFlux.
• Slot hierarchies can be partially exported by iterating the hierarchy manually, but this cannot include components and their values.
• As far as I know there is no way to access mesh data right now.

Additional Context

No response

Requesters

Nutcake

[epicEaston197]

This would be a ton of data for the post request node this might need to be split into its own separate node or wait until we have collections

[ghost]

I can already think of the first thing I would do if this is added