How do we deal with jsduck still being used in the release branches?

In T363905#9773574, @hashar wrote:

How do we deal with jsduck still being used in the release branches?

In general, jsduck is triggered via the CI job template extension-javascript-documentation which isn't defined for release branches, and e.g. its sub-job mwext-node18-docs-publish only runs for the master branch – so, once we've finally eliminated it from all master branches (still a work in progress!) this should suffice.

@Jdforrester-WMF sounds good thanks!!