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>

xtask/src/tasks/bindings/mod.rs

@@ -0,0 +1,26 @@
+// Copyright (c) Microsoft Corporation.
+// Licensed under the MIT License.
+
+pub mod all;
+pub mod c;
+pub mod cpp;
+pub mod csharp;
+pub mod ffi;
+pub mod go;
+pub mod java;
+pub mod python;
+pub mod ruby;
+pub mod version;
+pub mod wasm;
+
+pub use all::{BuildAllBindingsCommand, TestAllBindingsCommand};
+pub use c::{TestCCommand, TestCNoStdCommand};
+pub use cpp::TestCppCommand;
+pub use csharp::{BuildNugetCommand, TestCsharpCommand};
+pub use ffi::{BuildFfiCommand, TestFfiCommand};
+pub use go::TestGoCommand;
+pub use java::{BuildJavaCommand, TestJavaCommand};
+pub use python::{BuildPythonCommand, TestPythonCommand};
+pub use ruby::TestRubyCommand;
+pub use version::BindingsCommand;
+pub use wasm::{BuildWasmCommand, TestWasmCommand};