move large entity components to attachments and split control and data planes

Currently, the back plane conflates control and data concerns by sending both types of messages over the same bus. The requirements for each of these are different and as such, the back plane should be split to allow small control message to flow over a different bus than large data messages. Examples of the latter include executable archives, activation arguments, activation results, and activation logs. This is a requirement for enabling large file upload and large invoke/trigger payload which are currently limited in size.

This is an umbrella issue for necessary work items:
1. [x] move large entity components to database attachments
2. [ ] support streaming I/O through controller to database (and vice versa)
3. [ ] support streaming I/O through invoker to container (and vice versa)
4. [ ] do not pass payloads through control messaging layer
5. [ ] add support in CLI for working with large files when creating actions or activating assets
6. [x] support large zip/jar file uploads for actions