Add style checks

[rhuanjl]

1. Add in the style checks from the old CI
2. Update copyright check so all edited files have to have new copyright (also added the "All Rights Reserved" statement to the copyright in the license)
3. delete the defunct dotnet CI config script

I considered renaming the jenkins folder as it's nothing to do with jenkins - but there were a lot of things to change based on that and it seemed like too big a diff to be worth it.

For reference these "Style" checks do:

1. Copyright: check all edited files in the PR contain the correct copyright Banner
2. Ascii check: check all edited source code is ascii only (this is so anyone compiling on a machine from a different locale doesn't get errors)
3. EOL check: check all edited files use LF only line endings (no CR) this excludes .baseline files for tests which have to use CRLF due to an awkwardness of how testing works on windows
4. Tab check: check all edited source files contain no tab characters

For #6547
Fixes: #6548

[rhuanjl]

This instruction didn't work - edited to fix (by bringing in line with the logic in the other check scripts

[rhuanjl]

Test failure is a timeout on a wasm test - I did a re-run and it timed out again though on a different test - maybe just a slow time of night or something? (the runtests script counts any test taking more than 1 minut as a timeout and fails it)

[Fly-Style]

@rhuanjl @ppenzin BTW, I have a good experience with clang-format and integration it as GitHub Action for automated code formatting.
Probably, it's a good idea to discuss about migration to clang-format ... someday

[rhuanjl]

@rhuanjl @ppenzin BTW, I have a good experience with clang-format and integration it as GitHub Action for automated code formatting.
Probably, it's a good idea to discuss about migration to clang-format ... someday

Clang format for the whole repository could well be quite a significant change - the historic style checks that this includes are quite minimal and aimed at avoiding specific problems:

• tabs are banned because different editors make them different sizes
• line endings are LF only as it's more portable
• non-ascii code in source is banned because with different locale settings it can fail to compile
• copyright banners are forced for obvious reasons

A more extensive consistent style across the whole code base could be very nice for welcoming new contributors but how much work would it be? And how beneficially would it be? (That said if you'd like to try it and open a PR I'll take a look)

[ppenzin]

Aside from feeling ambivalent about MSFT copyright in new files, this looks good.

[ppenzin]

If you want to keep make it more future-proof, you can remove the name of the CI system we are using. I don't think it is critical, we can keep Azure here.

[rhuanjl]

done

[ppenzin]

I think you might still need exit 1, otherwise Azure may not pick the failure up.

[rhuanjl]

@ppenzin I've done the updates and exclude .yml from the copyright check so we don't have to say copyright microsoft in the CI script.