fix: Fixing help directory case ( Fixes #44 )

[StartAutomating]

Renaming help directory so the module imports cleanly on linux.

[jdhitsolutions]

Fighting case is an ongoing battle. I am hesitant to change the directory name since .NET returns en-US. What I should do is pay closer attention in the module files to make sure I match the directory case.

[StartAutomating]

@jdhitsolutions noted and interesting.

I did a bit more digging and it appears that the root of my issue is that Raspberry Pis stubbornly want to be British (en-GB).

Note the case :-)

This has me scratching my head a bit at whey "en-us" worked, and I suspect the answer is that PowerShell defaults to this somewhat explicitly.

Another way to handle this and be locale compliant should be putting the help in an "en" directory, which would work for en-US and en-GB on Linux.

Haven't yet gotten a way for my locale changes to stick on the Pi without changing them in my profile. Going to have to try to test it in a GitHub workflow and see if it works from there.

[jdhitsolutions]

I seem to recall a localization issue on another module with en-GB. The best solution might be to create the en-GB folder.

[StartAutomating]

Can confirm that it works on Linux after I switched the locale around.

Can also confirm that just changing it to "en" does not work (though I believe this to be a PowerShell issue).

I agree with your approach of duplicating docs into en-GB, if we want it to work "out of the box" on a Raspberry Pi.