[FEATURE] HTTP triggers - add Match path requests prop to filter requests

[vunguyenhung]

Is your feature request related to a problem? Please describe.
Some users faced an issue that their HTTP endpoint is called by crawlers for robot.txt
https://pipedream-users.slack.com/archives/CPTJYRY5A/p1715325204478109

Describe the solution you'd like
Add Match Path prop to HTTP triggers so they will only emit events for path that matched the specified path

Do you have a workaround?
Filter actions

[mroy-seedbox]

Ideally, this parameter should take in a list of regexes to match against, so that we can accept multiple paths.

Otherwise, even a single regex can allow us to enter multiple options, like this: (path1)|(path2)|(path3)|.... But I think an array would be more user friendly.

For example, we have HTTP triggers to which we add a Slack channel ID in the path. We should be able to use a regex in order to match against the Slack channel ID format (or even a list of known IDs from an env var), and filter out anything else.

Optional/bonus: also allow to filter based on the HTTP method (in a separate prop, of course).