Animations codemod - separate table as its own rule

[thatblindgeye]

From discussion of animations issues arising in product, we should update the current animations codemod so that there are 2 rules that must be manually run with the --only flag:

1. The existing codemod as it is, except remove Table from the rule
2. A new rule that only updates Tables to add the hasAnimations prop, and only when the Table is an expandable table (may have to check if at least 1 child of the table or the Table itself has isExpanded or a new propr isContentExpanded for this).

Alternatively, a nice-to-have that was mentioned during platform topics today was a CLI for the existing animations rule, where you select what components you want to opt into animations for. cc @wise-king-sullyman can explain better in case I missed anything/am off on what the idea is.

[gitdallas]

@wise-king-sullyman - seems a bit much to be like

you want it for FormFieldGroupExpandable?
how about DualListSelector?
how about TreeView?
how about AlertGroup?
how about SearchInputExpandable?
how about Table?

if Table is kind of an outlier here for concern, perhaps something like "This will update several React Core components. Would you like to update React Table as well? Note that some users have experienced issues with animations on Table."

[wise-king-sullyman]

Copying my comment from SoS here: just having table be the outlier is probably fine, but if we get any actual requests from consumers to make the others individually selectable in the code mod I would swing my vote back.