Some Windows environments have a severely restricted 256 characters
allowed for a 'comment'. When the 'user' and 'service' attributes are
lengthy (e.g., client IDs and URLs), this information can exceed the
limit -- particularly in the 'target == None' case (where both 'user'
and 'service' are duplicated).

To add to the trouble, the call to `credential.validate_attributes()`
before this function returns prevents a consumer from updating this
comment to be within the length limit.

Switch to a static string for this comment that is within any
reasonable length limit. If a consumer would like to add their own
more verbose comment, they can do so with `Entry::update_attributes()`
after the entry is created.

Note: a pass-through optional parameter for the comment value was
considered, but there's not really a good, obvious answer for a clean
API on Entry with such an approach. The 'comment' attribute also
appears to be Windows-specific. This approach should not have any
impact on consumers and certainly does not have an impact on the API.

An alternate-alternate approach may be possible with just removing the
call to `credential.validate_attributes()`, but I don't have the
expertise to understand what the effects of this would be.

This fixes #251 on Windows.

This omits the change to LazyLock, which would update the MSRV.

With this, we can release v3.6.3.

Updates the requirements on [windows-sys](https://github.com/microsoft/windows-rs) to permit the latest version.
- [Release notes](https://github.com/microsoft/windows-rs/releases)
- [Commits](https://github.com/microsoft/windows-rs/commits)

---
updated-dependencies:
- dependency-name: windows-sys
  dependency-version: 0.60.2
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

…/windows-sys-0.60

Update windows-sys to v60.