Feature to lock an overlay

[Jmr3366]

Closes #3414 by adding a locked option in overlay

Description of the Change

Extended the 2nd parameter offered in overlay.
Like zorder=<num> you can now add locked=<0/1>.
locked defaults to 0 (not locked)

Locked overlays appear in the Window -> Overlays menu but are greyed out and can't be unchecked

Possible Drawbacks

None

Release Notes

Examples:
[overlay("Test","zOrder=10;locked=1;"):[ { content to display }]

---

This change is 

[Jmr3366]

Is there a known process/procedure to mitigate this (sometimes it happens, other times not)?

[kwvanderlinde]

Is there a known process/procedure to mitigate this (sometimes it happens, other times not)?

You can avoid it by not using closing keywords in the PR (e.g., just write "#3414" instead of "closes #3414"). After the jobs run the description can be updated.

But I think we ought to remove the job until we know what's wrong with it.

[cwisniew]

Is there a known process/procedure to mitigate this (sometimes it happens, other times not)?

You can avoid it by not using closing keywords in the PR (e.g., just write "#3414" instead of "closes #3414"). After the jobs run the description can be updated.

But I think we ought to remove the job until we know what's wrong with it.

I am in two minds as when it works it means I don't have to do anything before merging, when it fails it at least reminds me to assign the label to the PR

Otherwise I end up spending too much time on release chasing down all the PRs and assigning them labels so the release notes get created correctly. Is it perfect no but it's better than when it wasn't there. Also please don't leave off the keywords that close PRs as that creates more work and I will soon get annoyed enough I will start rejecting them :)