Render graph binding and driver patterns

[attackgoat]

This is an open discussion on the existing patterns as of v0.4. I'll update this issue. Feel free to create a specific issue if you want to track a particular idea, even if it is mentioned elsewhere.

Status:

• Stability alpha: validly does all the things but some things can still be requested in a way that triggers validation errors
• API signature beta: some things are missing or implemented using incorrect patterns
• Documentation pre-alpha: feel free to comment "this area confused me" here and I would ❤️ to hear how/any feedback
• Performance/allocation optimization: not really started except for experiments and critical bits

Particularly lacking features:

• Full screen/swapchain-recreate bugs

Anything else:

• Comment on anti-patterns you see, impediments to contribution, etc.
• "This should be just a graph!" - Well, maybe it should - what would that look like to you?
• Success? Like the patterns? Help perfect them!

Thank you!

[attackgoat]

Bindings could be removed as a concept if we store the resource state using the private data extension. That way each image/buffer/accel would be given the appropriate barriers without having to "hold" the binding and then return an "updated" one on unbind.

I think the end result would be basically bind-by-reference instead of bind-by-value; and this would definitely simplify usage patterns for no appreciable downside.

Update: See #25

[attackgoat]

When figuring out what kind of cache types are offered, it would be helpful to distinguish between swapchain images and "regular" images because this one class of resource is always a known size. See https://github.com/attackgoat/screen-13/pull/13

The design should support for multi-monitor setups too.

Update: See #29

[attackgoat]

Closing as all items, except for documentation, have been addressed. The remaining rough spots will be handled with individual issues.