Update performance component to match bugzilla changes

[davehunt]

The Core::Performance component was renamed to Core::Performance General in https://bugzilla.mozilla.org/show_bug.cgi?id=1953893. We should update the moved_to_performance rule to reflect this change.

[davehunt]

I think this requires changing "Performance" to "Performance: General". We may also want to update the templates here and here to reflect the new component name.

[suhaibmujahid]

We should update the moved_to_performance rule to reflect this change.

@davehunt Should this rule now only target the Core::Performance: General component? Do you want to cover the new components as well?

We have the Core::Performance in a skip list to be excluded from workflow rules like P1 bugs with no assignee and missing severity. Do you want to add the new components to the list?

[davehunt]

@Bas-moz what do you think? Should the needinfo be set for any bugs moved to a performance component, or a subset? Perhaps each component should have its own template?

I'm not sure about the skip list question. Do we know why Core::Performance was in this skip list? Perhaps we can just remove this?

[suhaibmujahid]

Do we know why Core::Performance was in this skip list? Perhaps we can just remove this?

Perhaps @calixteman has the answer. It was introduced in #613 a long time ago, but it seems that it was never included in the workflow rules (#325). I suggest removing it for now; we can always restore it if necessary.

[calixteman]

Do we know why Core::Performance was in this skip list? Perhaps we can just remove this?

Perhaps @calixteman has the answer. It was introduced in #613 a long time ago, but it seems that it was never included in the workflow rules (#325). I suggest removing it for now; we can always restore it if necessary.

Sorry I don't remember exactly.
As far as I can tell, we wanted to move slowly to not be too much disruptive, so it isn't impossible we just postponed removing it from the skip list and then we forgot...