Add the ability to constrain actions by type

[selfcontained]

Description

It would be helpful to have the ability to constrain actions by type as well as the other existing constraint properties. This would allow slightly more flexibility for routing specific types of actions to certain handlers. Being able to constrain by type allows you to route actions that may have different types but the same callback_id (or other constraint properties), or even route all actions of a specific type to one handler (regardless of callback_id, action_id or block_id. Sharing things like a callback_id across different action types sounds weird at first, but I've bumped into some places where this would be useful.

What type of issue is this? (place an x in one of the [ ])

• bug
• enhancement (feature request)
• question
• documentation related
• testing related
• discussion

Requirements (place an x in each of the [ ])

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

[stevengill]

This makes sense to me. I've definitely had to reuse an actionID on multiple actions even though our docs say it should be unique.

Not sure what if any unattended consequences could arise from offering more contraint options.

[stevengill]

PR has been merged. Closing issue