feat(xtask): consolidate CI workflows onto xtask helpers (#542)

- split the xtask crate into structured modules for
  - bindings
  - ci
  - dev
  - util
  - no-std
- Adding commands for
  - ci-release/ci-debug
  - MUSL/no-std
  - per- binding language smoke tests
  - developer tasks (fmt, clippy, pre-commit, pre-push)
- refresh Cargo manifests/locks, binding readmes, and shared FFI helpers so every binding reuses the same preparation steps
- refactor GitHub Actions (release/debug, extensions, CodeQL, clippy, bindings) to call the new xtask commands
- Use rust-cache in ci workflows (microsoft qdk also does this)
- extend README with a contributor workflow section describing how xtask mirrors CI expectations
- update pre-commit and pre-push hooks to use the xtask dev commands

WORKAROUND:
When dotnet is run from an xtask, codeql tracer intercepts it an routes to a nonexistent binary.
Therefore in codeql workflow, xtask is not used for c# and instead dotnet is directly invoked.
Tracked by #545

closes #475

Signed-off-by: Anand Krishnamoorthi <anakrish@microsoft.com>

scripts/pre-commit

@@ -4,25 +4,4 @@
 
 set -eo pipefail
 
-if [ -f Cargo.toml ]; then
-    # Ensure that all targets can be built.
-    cargo build --all-targets
-
-    #Ensure that code is correctly formatted.
-    cargo fmt --check || (echo "Run cargo fmt to fix formatting" && exit 1)
-
-    # Ensure that clippy warnings are addressed.
-    cargo clippy --all-targets --no-deps -- -Dwarnings
-
-    # Ensure binding versions reflect the staged changes.
-    cargo xtask bindings --check
-
-    # Ensure that all modifications are included.
-    # TODO refine status checking.
-    if git status -s | grep -e "MM " -e "??" -e "AM " -e " M "  > /dev/null; then
-	printf "\nUnstaged changes found:\n"
-	git status -s | grep -e "MM " -e "??" -e "AM " -e " M "
-	echo "Stage them and try again"
-	exit 1
-    fi
-fi
+cargo xtask pre-commit