docs: align users-groups example YAMLs with comment text

[0xdeadd]

Proposed Commit Message

docs: align users-groups example YAMLs with comment text

Examples 3 and 4 in the cc_users_groups module docs describe
behavior (password-based login rejected, SSH access for the GitHub
user TheRealFalcon and the Launchpad user falcojr) that the actual
YAML examples didn't include.

Add the missing lock_passwd and ssh_import_id fields so the
rendered example matches the prose. Inline-array syntax for
ssh_import_id matches the existing convention in
cc_ssh_import_id/example1.yaml and cc_users_groups/example7.yaml.

Fixes GH-6857

Summary

The example3 and example4 comments in doc/module-docs/cc_users_groups/data.yaml describe two behaviors that are missing from the corresponding YAML files:

1. "Password-based login is rejected" → lock_passwd: true was absent
2. "the GitHub user TheRealFalcon and the Launchpad user falcojr can SSH as newsuper" → ssh_import_id was absent

This PR adds the two fields to both example3.yaml and example4.yaml so the rendered docs match the prose.

Test Plan

• No code changes — docs only
• YAML still parses (verified locally)
• Inline-array form for `ssh_import_id` matches existing examples in `cc_ssh_import_id/example1.yaml` and `cc_users_groups/example7.yaml`

Checklist

• CLA — will sign at https://ubuntu.com/legal/contributors when prompted
• Commit message follows conventional-commits format
• Change is small and scoped to the docs fix
• References issue (Fixes [docs]: Users and Groups module schema examples code blocks differ from explanation text #6857)
• No new behavior, so no unit tests needed

Fixes #6857

[blackboxsw]

thank you for the submission @0xdeadd. I believe we already have a pull request in progress that is attempting to address this fix in #6858. If there is something else not covered in that pull request please feel free to comment on that PR instead. I'll close this PR in the meantime while we await resolution and merge of the prior PR.

[neitsab]

I had pondered as well about the "Password-based login is rejected" in example 3.

I left it alone in my PR because the docs say it is true by default (and so not having it in the code example does not exactly qualify as a bug), but it's true that I found it a bit puzzling at first why the explanation would say "Password-based login is rejected" and then not have a matching directive.

So maybe this PR can be amended to build upon mine (that has now been merged) and simply add lock_passwd: true to example3.yml to make it really explicit, even though it's the default?