Add support for injecting arguments & intent extras in presenters

[BenHenning]

We have a bunch of places where we retrieve fragment arguments and activity intent extras in presenters, but it should be possible to inject these or at least introduce argument/intent management infrastructure to facilitate injection or retrieval to simplify managing these dependencies (& centralize requiring them to avoid needing to make this decision for each fragment and activity).

[BenHenning]

NB: This probably is only possible using custom code generation (e.g. with a custom KSP annotation processor). I started prototyping something along these lines (for activity generation) a couple months back--it should be straightforward to figure out the constituent pieces if we can determine what code needs to be generated.

That being said, #1051 touches on this from a data-oriented perspective. Combined with thoughts around generate code generation for base activity/fragment/view classes, perhaps the best approach here is actually to just use a single proto for activity/fragment/view construction and be able to inject this, then have separate properties annotated for configuration and app death retention. This would be incredibly robust, and is something we can build into the broader system of base class generation.