Runtime disabling of specific input type tracking

[Shute052]

Objective

• Parts of completing Refactoring underlying architecture to support various input types #483

Allow disabling of specific input type tracking.
This can be especially useful if users encounter conflicts with input handling from other crates not currently integrated yet.

Solution

Add TrackingState enum for always enabling, always disabling, or ignoring once for input type tracking.

Add a new resource called TrackingInputType, which includes flags for enabling specific input type tracking.

Furthermore, add run conditions that are active when the TrackingInputType is enabled for specific input types.

Changelog

• Added TrackingState enum
• Added TrackingInputType Resource
• Exported new items into the prelude module
• Extracted prioritize_ui_input and prioritize_egui_input systems from update_action_state
• Integrated new systems into InputManagerPlugin
• InputStreams now take Option for gamepad values

[Shute052]

@alice-i-cecile This isn't related to #185, but could you take a look at the parts about configure_sets? I'm not sure if it's going to work like I expect.

[alice-i-cecile]

Okay, I definitely think this is a useful tool, and I really like the notion of having a way to keep track of which input streams we're subscribed to.

However, I don't want to add more complexity/features to the code until #321 is solved. I think that this is helpful to shape that sort of design though.

[Shute052]

I'm also in favor of splitting InputStreams and converting UserInputs into traits.

[Shute052]

Blocked until the new architecture has been implemented

[alice-i-cecile]

Closing: this will be easier to redo.