Expose LOCK response ETag on NKLock

[Copilot]

NKLock did not surface the resource ETag already returned by successful WebDAV LOCK responses, forcing callers to operate without metadata that was already available in the response body. This change keeps the existing lock/unlock flow intact and makes the parsed LOCK ETag available directly on the lock model.

• Model update

  • Add etag: String? to NKLock.
  • Parse d:getetag from the existing LOCK XML payload in NKLock.init(xml:).
  • Normalize the value by stripping surrounding double quotes, matching existing ETag handling elsewhere in the library.
  • Extend the raw-value initializer with a trailing etag parameter defaulting to nil to preserve source compatibility.

• Parsing behavior

  • Missing d:getetag continues to produce a valid NKLock.
  • Unquoted ETags are preserved as-is.
  • No additional WebDAV request is introduced.

• Unit coverage

  • Add NKLockUnitTests for:
    • quoted ETag parsing and normalization,
    • missing ETag behavior,
    • unquoted ETag preservation,
    • lock token parsing from a valid LOCK response.

let lock = NKLock(data: lockResponseData)
let etag = lock?.etag // "etag-after-lock"

[Copilot]

Pull request overview

Exposes normalized LOCK response ETags through NKLock without changing request behavior.

Changes:

• Adds optional etag parsing and raw initialization support.
• Adds tests for quoted, unquoted, and missing ETags.

Reviewed changes

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

File	Description
Sources/NextcloudKit/Models/NKLock.swift	Adds and populates the optional ETag property.
Tests/NextcloudKitUnitTests/NKLockUnitTests.swift	Covers LOCK token and ETag parsing behavior.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.