feature: capabilities devex

[nick1udwig]

Is your feature request related to a problem? Please describe.
Its fiddly to get capabilities to work properly

Describe the solution you'd like
Two things that could be improved to make them less fiddly:

1. Reduce number of places they must be declared/specified. Currently need to specify in manifest.json/scripts.json as well as in the file itself, where they are attached to the message.
2. Improve visibility when debugging. Currently, parsing them in the event loop is possible, but not easy or good devex.

Some suggestions of some possible ways work towards these to get creative juices flowing:

1. Make it easy to attach all caps held by our process to a message. Or perhaps: all caps we have that are issued by the target process. The first possibility leads to a risk of leaking caps to nefarious third parties (since they can save them); so perhaps we'd need a concept of a "read only" capability. The second (auto attach all caps for a target) wouldn't have this problem. The downside here is that we are sending more information with each request. If you limit to local only, this might not be a huge problem, but still will lead to a performance hit.
2. Add some way to print attached caps with messages in event loop.

[nick1udwig]

Realized 2 already exists. 1 might be a nice process_lib function.

[nick1udwig]

Resolved in hyperware-ai/process_lib#120 #619 ; will close issue once those are merged.