fix: add support for preserving quoted group names in sshd_config

[Gijsreyn]

PR Summary

Fixes a bug where sshd_config list keywords with quoted, space-containing values (e.g. the Windows group "openssh users") were split into separate entries on export and get.

PR Context

Fixes #1508.

[Copilot]

Pull request overview

This PR fixes a Windows-specific parsing/export bug in the Microsoft.OpenSSH.SSHD/sshd_config resource where space-containing, quoted list entries (e.g. AllowGroups administrators "openssh users") were incorrectly split into separate items during get and export.

Changes:

• Added a Pester test that verifies get and export preserve quoted group names containing spaces.
• Updated get_sshd_settings() to prefer explicitly-parsed config-file values for space-separated multi-arg keywords (avoiding sshd -T quote-stripping/splitting behavior).
• Added Rust unit tests covering the new override behavior.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
resources/sshdconfig/tests/sshdconfig.get.tests.ps1	Adds coverage ensuring quoted group values remain a single array entry for both get and export.
resources/sshdconfig/src/get.rs	Restores correct list semantics by overriding sshd -T-normalized values with explicitly parsed config values for affected keywords.

[Gijsreyn]

@tgauth - is this something you can take a quick look at?

[tgauth]

Thanks for opening this! My initial thoughts are that this issue is applicable to other arguments that can have spaces as well (i.e. regular arguments for paths) and I wonder if we can address those here as well. I'm going to think on it a bit and see if there's a good way to do that, and if not, we can defer it to a future PR.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[tgauth]

Ok to cover broader cases, I think there's two changes needed:

1. Expand this check to be any keyword in explicit_settings that has spaces, rather than only checking for keywords in MULTI_ARG_KEYWORDS_SPACE_SEP
2. When the Rust parser is parsing keywords from sshd -T, it should not error on "regular, single-value" keywords with a spaced value (i.e. Banner "C:\Program Files\ssh\sample_banner.txt" is output as Banner c:\program files\ssh\sample_banner.txt which seems like Banner has two args "c:\program" and "file\ssh\sample_banner.txt" so the parser errors currently. We should have the parser combine them into a single value)

@Gijsreyn, if you want to leave the PR as-is and then I'll add these changes after, that's fine with me too!

[Gijsreyn]

@tgauth - thanks for the feedback! I tried to incorporate it already into this PR. Let me know what you think :)