fix: ASSOC crash, ARM64 WOW64 detect, LibreWolf downloads, Core Isolation warning

[Longno242]

Fixes a few small issues:

• ASSOC.ps1: skip Shell32 substring if the search string isnt found (crash on some locales)
• LIBREWOLF.ps1: check curl exit codes
• ARM64: also check PROCESSOR_ARCHITEW6432
• playbook: note that disabling Core Isolation breaks WSL2/Docker ([BUG] - WSL fails to launch with ERROR_PATH_NOT_FOUND #1615)

[jacksyrm]

The ARM64 changes look good. A couple of things with the rest:

For ASSOC, skipping the substring avoids the error, but leaves $userExperience empty. We then carry on replacing the associations with a hash that's missing part of its input. Could we stop before touching the registry if we can't find the string? The closing } needs checking too. This applies to both copies of the script.

The curl checks also need --fail on both commands, otherwise a 404 can still return exit code 0.

I'd leave out the WSL2/Docker warning for now. This option disables VBS features, but doesn't turn off the hypervisor or Virtual Machine Platform. I don't think #1615 gives us enough to say this checkbox breaks them.

[Longno242]

Thanks for the review. Changes are in d6ff647:

• ASSOC (both copies): if the user experience string or its closing } can't be found in Shell32.dll, the script now prints a message and exits before touching the registry, instead of continuing with an empty value.
• LibreWolf: added --fail to both curl downloads, so an HTTP error like a 404 now gives a non-zero exit code.
• Core Isolation: removed the WSL2/Docker warning from playbook.conf and script-core-isolation.yml.

The ARM64 changes are unchanged.