chore(build): sync Jest version across plugins

[hainenber]

chore(build): sync Jest version across plugins

SUMMARY

I noticed a newly added plugin still use old Jest version v26 versus current one of v29. This PR is to rectify that and to ensure generated plugin in future will have Jest v29 as dev deps.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

All CI checks pass

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[michael-s-molina]

Maybe this is a good opportunity to make Jest a peer dependency and also use * as the version because we want future bumps of Jest to also be applicable to plugins.

[hainenber]

I'm not sure if specifying Jest as peerDeps would be correct since the library is used for development only and for the plugin's operations. If there's anything akin to peerDevDependencies, it'd be more suitable :D

I mean, yeah, it'll be super satisfying for a single future Jest/Storybook/Babel bump to impact all plugins but I feel it's a little bit trading off correction for convenience. I'm not sure how to articulate this point, tbh

[michael-s-molina]

If there's anything akin to peerDevDependencies, it'd be more suitable :D

Yeah, that would be the ideal solution. I believe that with current limitations, correction beats convenience so you can ignore my suggestion.