Restore the ability for button-based navigation to ignore navigation locks.

[FrenjaminBanklin]

Reverses/amends the solution for #775.

It's easy for content authors to create situations in which end users can become stuck in a certain page due to navigation being locked. Previously, nav:goto triggers were able to bypass navigation locks which, in some cases, would cause problems and, in other cases, solve problems.

In practice, that behavior ended up becoming load-bearing. Existing content can now be assumed to have the expectation that buttons using the nav:goto trigger will assume that navigation will still work regardless of being locked.

Either rewind the fix and allow nav:goto triggers to ignore navigation locks again, or embellish such events with an extra configurable property which makes it explicit that the buttons will respect any locks on the navigation.

See https://github.com/ucfopen/Obojobo/pull/1911/files as a reference for what changed to disable the previous behavior.