Packages are not in sync with upstream tutor releases

[CodeWithEmad]

tutor v22 was released last week.
Can we think of a process or solution to keep the packages up to date with the tutor releases?
Does it make sense to drop the "<v22.0.0" and only keep the ">vx.x.x"?

@feanil @arbrandes

[arbrandes]

This is a per-plugin decision, but broadly speaking, I think it's safer for a plugin to declare an upper version limit. It's like saying, "we have only tested up to this version; no guarantees above that!". Then once the plugin is tested against a newer Tutor - maybe by a user such as yourself - we can bump it.