This change moves the library crates, which don't have an executable,
into the `lib` folder. This makes discovering shared libraries easier,
instead of relying on the `_lib` convention the crates use. This change
doesn't rename the libraries, it only moves them.

This change doesn't require modifying any code or cargo manifests,
except for pointing to the correct path in the virtual workspace.

This change moves the resource subprojects, which have an executable,
into the `resources` folder. This makes discovering which projects
provide DSC resources easier, instead of checking whether the folder
contains any resource manifests. This change doesn't rename the folders,
it only moves them.

This change doesn't require modifying any code or cargo manifests,
except for pointing to the correct path in the virtual workspace and
build script.

This change moves the adapter subprojects, which have an executable,
into the `adapters` folder. This makes discovering which projects
provide DSC resource adapters easier, instead of relying on the
`-adapter` suffix convention. This change does rename the folders,
dropping the suffix. The adapters aren't rust crates, so this doesn't
affect code compilation.

This change doesn't require modifying any code or cargo manifests,
except for pointing to the correct path in the build script.

This change moves the tree-sitter subprojects, which define grammars,
into the `grammars` folder. This makes discovering which projects
provide DSC grammars easier, instead of relying on the `tree-sitter-`
prefix convention. This change does not rename the folders, it only
moves them.

This change doesn't require modifying any code or cargo manifests,
except for pointing to the correct path in the build script and
virtual workspace manifest.

This change also updates the `.gitignore` to generically ignore
generated grammar files in the `grammars` folder.

This change renames `dsc_lib` to `dsc-lib`. This is done for
a few reasons:

1. The general naming convention for rust crates is `kebab-case` for
   crates, `snake_case` for modules. This aligns the naming convention.

   Note that kebab-case crate names are still referenced with underscores
   as `snake_case`, so no code needed to be changed in crates, only the
   cargo manifests.
1. When we eventually publish the library crates, we will need to use a
   coherent naming convention. Standardizing on `dsc-lib` as a prefix
   ensures that the other library crates can follow this convention and
   more readily be discovered and collected. The other libraries are only
   intended for use with DSC.

This change ensures that the manifests and build script are updated to use
the renamed crate. I decided to keep a 1:1 map of crate name and folder,
to limit confusion over having more than one `dsc` folder in the project.

Prior to this change, the discovery tests referenced the path
to test files for the PowerShell adapter by folder. This change
corrects those paths to their new location.

This change updates the WMI adapter test to point to the
correct location for the test configuration after the folder
move and rename.

… for WinPS

Prior to this change, the adapter munged the PSModulePath by
removing any path items containing the segment `\powershell\`
to ensure no PowerShell 7 modules are used for discovery when
invoked with the Windows PowerShell adapter.

This implementation was highlighted as a bug after moving and
renaming the `powershell-adapter` folder to `adapters/powershell`.
The tests showed that none of the test modules in the `Tests`
subfolder were discovered by the adapter.

The prior implementation removed not only the actual PowerShell 7
module paths, but _any_ module path with `powershell` anywhere in
the ancestor folder path. Not only does this cause the tests to
fail, but it also prevents users from discovering any modules
they might have added in custom locations like `~\dev\powershell`
or `D:\Tools\PowerShell`.

This change updates the implementation to specifically search for
and remove the default module paths for PowerShell _if_ PowerShell
is installed. It no longer uses a simple match for any path that
contains `powershell` as an ancester folder.

This change renames the `osinfo_lib` crate to `dsc-lib-osinfo`.
This is to support eventual publishing of the crates. This crate
is a dependency not only for the `osinfo` resource but also the
`dsc-lib` crate. When we implement the Rust RDK, we will need to
publish the library crates, and this ensures the naming is both
consistent and easily discoverable.

This change makes the requisite updates to cargo manifests, Rust
code, and the build script.

This change renames the `pal` crate to `dsc-lib-pal`. This is to
support eventual publishing of the crates. When we implement the
Rust RDK, we will need to publish the library crates, and this
ensures the naming is both consistent and easily discoverable.

This change makes the requisite updates to cargo manifests, Rust
code, and the build script.

This change renames the `registry_lib` crate to `dsc-lib-registry`.
This is to support eventual publishing of the crates. This crate
is a dependency not only for the `registry` resource but also the
`sshdconfig` resource. When we implement the Rust RDK, we will need
to publish the library crates, and this ensures the naming is both
consistent and easily discoverable.

This change makes the requisite updates to cargo manifests, Rust
code, and the build script.

…y_context`

This change renames the `security_context_lib` crate to
`dsc-lib-security_context`. This is to support eventual
publishing of the crates. This crate is a dependency not
only for the `registry` resource but also the `dsc-lib`
crate. When we implement the Rust RDK, we will need to
publish the library crates, and this ensures the naming
is both consistent and easily discoverable.

This change makes the requisite updates to cargo manifests, Rust
code, and the build script.

Prior to this change, the Rust crates for specific DSC
resources used the binary name as the crate name. This
causes a few problems:

- When using `cargo` commands with the `--package`/`-p`
  option to limit which workspace packages to use for
  an operation, some of the packages, like `registry`,
  conflict with dependencies of the same name.
- If we eventually publish any of these crates, they are
  not obviously related to DSC and might be mistaken as
  general purpose tools, which we don't currently plan to
  support.
- It isn't obvious in the cargo lock file whether an item
  is for a workspace package or an external package.

This change:

1. Renames the resource crates to `dsc-resource-<name>`.
1. Defines an entry in the `bin` table for the cargo manifest
   to ensure that the binary name remains the same as it was
   before the change. We _may_ want to consider renaming the
   binaries in a future, potentially breaking change, so it
   is always obvious when a resource is builtin / which binary
   to use.

This change has no effect on the build scripts or workspace
manifest, since we explicitly point to folder paths instead of
using crate names.