Prepare the FabricBot config for migration to Policy Service

[jeffhandley]

There are changes that need to be made to the FabricBot configuration before this repository is ready for migration to Policy Service. There is some lost functionality here, but it was minimized as much as possible.

1. There were two tasks configured as event triggers that relied on noActivitySince that were removed
   • This relied on behavior of checking "no activity since X days, before this event," which is not a supported feature in Policy Service
   • In both cases, the automation would respond to the event on an issue that was stale before that event occurred
   • This automation is lost here and is not supported in the new service
2. There was a task that filtered away issues that have been added to any GitHub Project (Classic), and that condition is no longer supported
   • The new service does not support automation around GitHub Projects (Classic)
   • This task was changed to skip that condition to apply the 'needs triage' label even if the issue is on a project
   • References to project events were also removed from the configuration, but they did not previously have an effect
3. Explicitly filter for 'isPr' and 'isIssue' on all events
   • FabricBot used the "event_type" configuration setting to implicitly apply a filter, but the migration to Policy Service would lose that implicit filter
   • An explicit filter was added to add tasks where it otherwise could have been ambiguous
4. A disabled task was deleted, as was a test task

@ReubenBond Sorry for the loss of functionality here, we did our best to minimize it.

/cc @wtgodbe @mkArtakMSFT @JohannesLampel

Microsoft Reviewers: Open in CodeFlow

[ReubenBond]

No problems, @jeffhandley - thank you for helping us with this!