I _also_ thought this had been fixed; but Codacy is _still_ bothering me with the details. Note: my local `remark` currently doesn't complain about any other issues, so I'm re-submitting, to see if Codacy's `remark` still finds any excuse for complaining...
Ok, now it's Codacy complaining about a lot of things. This will require a _lot_ more work; there are a gazillion outstanding 'issues', most of which might be safe to ignore, others could improve performance and/or security, and a few are indeed critical and require being addressed... which is for another PR.
I didn't even notice that there _was_ a testing framework, which uses a 'special' SL account to log in, etc. Sadly, the way the login information is passed to GitHub Actions is anything but obvious; as such, this will be my last experiment — I'll skip the testing part if this doesn't work. After all, AppVeyor will run all the tests properly...
Due to an intermediate merger with upstream code, I lost my .editorconfig configuration; this meant that new YAML files were included with TABs, not the required spaces (arrrgh!!) and that required manual fixing, too.
I also restored .editorconfig and tweaked it to guarantee uniformity in spaces/indents — this might be useful for others running editors/IDEs that comply with .editorconfig (and even GitHub will comply with the .editorconfig rules when editing files online!)
On a different project, adding the dotnet.yml framework and specifying a version of .NET to run (6.0.X in this case) managed to get the automated scripts to finish with success. Let's see if the same 'magic' happens here.
Appveyor uses `remark` to throw a few warnings about lack of consistency when writing Markdown text; this README.md is now rewritten according to `remark`'s guidelines.
A `LibreMetaverse.ReleaseNoGUI.sln` was included at the root to allow Linux/macOS compilations to succeed, without worrying about the GUI apps.
To-do: create a more complex dependency logic so that Windows users automatically get the GUI apps compiled by default, while these are skipped under macOS/Linux. Currently, you need to explicitly use a different solution file.
Also: added information regarding upcoming obsolescence of .NET 5.0
In order to get successful builds under Linux/macOS, as well as properly packaging, this new solutions file was created. I'll update the instructions shortly.
