Labeling with other triggers

Description:
The current autolabeler action primarily supports labeling for pull_request events only. My proposal is to enhance this action to also support other types of GitHub events such as push, issues, and schedule, allowing it to automatically apply labels in these scenarios as well.

Justification:
Many workflows could benefit from automated labeling not only on pull requests but also on other events like pushes to specific branches or the creation of issues. In my case, I have workflows triggered by push events that automatically create pull requests. I intended to have labels applied within the same workflow, but currently, labels cannot be added because pull_request events are not triggered by pull request creations from workflows. Additionally, in push events, the event payload does not include the pull request information, resulting in the workflow handling it as "no branch" and thus failing to apply labels. This feature would enable GitHub Actions users to utilize labeling more flexibly and effectively across their projects, especially in automating workflow steps that are currently disjointed due to event limitations.

Are you willing to submit a PR?
I have not developed actions before, but I am willing to contribute to the implementation of this feature with the appropriate support and guidance.

Start by reading the action's event-handling and labeling logic to understand how pull_request payloads are currently processed. Define how push, issues, and schedule events should provide labelable targets, then add coverage for those event types and verify that labels are applied in the stated workflow scenarios.