Allow TeamLabelInference to trigger on bot actions

What does this MR do and why?

The TeamLabelInference handler doesn't apply the stage and section labels when a community member is using @gitlab-bot label because the bot explicitly ignores itself.

Allowing it to trigger in these cases could prevent some frustration (like here: gitlab-org/gitlab#410178 (comment 1382270286)) because then the stage and section labels would be added automatically and don't need to wait for a scheduled policy to take care of them.

Expected impact & dry-runs

These are strongly recommended to assist reviewers and reduce the time to merge your change.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/tree/master/doc/scheduled#testing-policies-with-a-dry-run on how to perform dry-runs for new policies.

See https://gitlab.com/gitlab-org/quality/triage-ops/-/blob/master/doc/reactive/best_practices.md#use-the-sandbox-to-test-new-processors on how to make sure a new processor can be tested.

Action items

• If adding environment variables for reactive processors, update config/triage-web.yaml and .gitlab/ci/triage-web.yml
• (If applicable) Add documentation to the handbook pages for Triage Operations =>
• (If applicable) Identify the affected groups and how to communicate to them:
  • /cc @person_or_group =>
  • Relevant Slack channels =>
  • Engineering week-in-review