Keep jQuery as dependency of prototype when migrating to v13

[lfdebrux]

note - look at Step by step ticket before this one: #1730

What

Add jQuery to the list of dependencies of v12 that are not included in new prototypes with v13, but which we keep for the user when migrating an old prototype.

Why

If a user is relying on jQuery for an old prototype, we don't want them to have to figure out why their prototype isn't working when they've migrated it.

Who needs to work on this

Developer

Who needs to review this

Developer

Done when

• Prototypes migrated with CLI tool have jQuery as a dependency at the end

[joelanman]

I'm not sure how easy this might be - jQuery wasn't a plug-in previously, it was included in the assets folder and made available at /public/... So even if we add jQuery as a plug-in, wouldn't it still be broken unless changes were made to the jquery path in the front end?

Another point is I'm not sure how many people actually use jQuery, my impression is its quite low

[lfdebrux]

I'm not sure how easy this might be - jQuery wasn't a plug-in previously, it was included in the assets folder and made available at /public/... So even if we add jQuery as a plug-in, wouldn't it still be broken unless changes were made to the jquery path in the front end?

We support jQuery specially, see #1478