Firefox-only: Update NSCL to 13.6.27.901, Fix TypeError: newTarget is not a function (SyncMessage.js:710:26)

Update NSCL that improves handling of script injections, especially failure management, transition handling and performance.

Redesign of the mechanism to obtain information about the API calls by page scripts used by FPD and popup to improve the performance, mainly in Firefox
* Ensure that by disabling JSS and FPD, the extension does not interfere with the page scripts (issue 176)
* Improve performance of timestamps spoofing
* Chromium-based browsers: Improve spoofing of decimal parts of floats (related to timestamps spoofing)
* Normalize domain names (treat domains name with trailing dot the same as without the dot)
* Change references to Pagure to Codeberg as we swithed the git repository provider

Fix issues with translation strings introduced in 0.20.3
ru translation at 100% again

More robust SyncMessage implementation
Prevent patchWindow from throwing on SOP violations.
Work around issue that could have prevented XML documents from being parsed/loaded by the browser (see also https://bugzilla.mozilla.org/show_bug.cgi?id=1899786)
minimal requirements increased to 115

Improve performance of FPD in temporary background scripts: Limit the amount of data that is stored to the permanent storage as well as the number of write operations without a real hit stemming from the need to recomupte the data.

Updated NoScript Commons Library dependency to the mv3 branch.
Fixed UI popup failing to render when opened first time after long inactivity

Fix the scope where updateCount used by FPD is created (Pagure issue 141. Although the function was not visible to page scripts, page script could have define their own function with several consequences as JShelter would call the page script function:

FPD would not learn about the calls and consequently would not detect fingeprinting attempts by the page,
pop up would not show calls to the wrapped APIs,
the page would be able to detect that JShelter is being installed,
if the page would not expect that someone is calling its function it can have any undesired consequences.

The bug was present in JShelter since the introduction of FPD in 0.6 and all versions up to 0.18 are affected.

Migrate to non-persistent background pages as a first step towards Manifest v3. Please report any unusual behaviour.

* Added support for built-in tweaks for specific domains. The goal is to list several domains that
break unnecessarily. Typically, an addition to the list should be well explained and must not
lower protection. A nice candidate is WebWorker and the protection of Strict (break) and Remove.
* Updated translations
* Improved FPD report based on user feedback:
* Do not refresh report automatically when tracking callers but introduce an update button so that
users refresh when convenient (prevent glitches in the interfaces)
* Add buttons to hide/show details and fold/unfold groups
* Do not show traces in bold to better differentiate between API names and traces.
* Add possibility to forget current traces. Useful when there is a fingerprinting script that activates after some action. The button allows the user to hide the traces triggered in the past and later load only new traces.
* Add support for signing for Android on AMO: https://blog.mozilla.org/addons/2023/10/05/changes-to-android-extension-signing/, so we needed to increase minimal supported version

* Remove Workers in Recommended JSS level to make JShelter compatible with some pages. This change might be reverted when [Pagure issue 80](https://pagure.io/JShelter/webextension/issue/80#comment-852202) is solved.
* FPD: Add possibility to learn the calling stack of functions that lead to the tracked APIs ([Pagure issue 52](https://pagure.io/JShelter/webextension/issue/52)). This information can be used to create block list or to study the calling code and its effects.
* FPD: Fix browser overloading by FPD messages by HTMLElement.prototype.offsetHeight and offsetWidth wrappers that might have crashed browsers.
* FPD: code cleanup

* Fix window.name protection, do not clear the property in the first visited page see https://pagure.io/JShelter/webextension/issue/116#comment-875070 for more details. The fix affects all Chromium-based browsers and Firefox installs with the protection active (by default it is off in Firefox as Firefox contains the protection since Firefox 88). This fixes, for example, reCaptcha.
* options: Improve space distribution, see https://github.com/polcak/jsrestrictor/pull/204#issuecomment-1727519706

* Update NSCL to uses built-in and faster function to compute sha256.
* Russian translation added.

* Added support for internationalization, Czech translation added, see blog post for instrctions for translators
* All texts revisited, clarified, and fixed grammar and typos
* Improved performance of Canvas and Audio little-lies wrappers by executing in WebAssembly, there will be a separate blog post with additional explanations. See the bachelor thesis of Martin Zmitko for more details.
* Improved performance of FPD. See the bachelor thesis of Martin Zmitko for more details.
* Expand description of the wrappers applied when the user interacts with the tweak GUI (suggested by the Plain Text UX review)
* Make level names in main options section stable width
* NSCL updated:
Prevent dead object access on using backward/forward cache of the browser
Fixed property/function mismatch

Improve performance of the code injection. See the bachelor thesis of Martin Zmitko (https://www.vut.cz/en/students/final-thesis/detail/147218) for more details.

* The code is no longer generated in the background due to the latency of passing huge messages from
background to content scripts.
* Optimize injection code size (remove duplicate code).

* Reimplement AudioBuffer.prototype.copyFromChannel to prevent multiple farbling of the same data
* Optimize performance of Canvas and Audio wrappers
* NSCL updated: JShelter benefits from the mechanism to prevent inconsistencies / breakages when the extension gets updated and therefore the old wrappers are invalidated by Firefox which nukes their sandbox and new ones are installed on extension's automatic restart