This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [golangci/golangci-lint](https://togithub.com/golangci/golangci-lint) | minor | `v1.51.2` -> `v1.52.1` |

---

### Release Notes

<details>
<summary>golangci/golangci-lint</summary>

### [`v1.52.1`](https://togithub.com/golangci/golangci-lint/blob/HEAD/CHANGELOG.md#v1521)

[Compare Source](https://togithub.com/golangci/golangci-lint/compare/v1.52.0...v1.52.1)

1.  misc.
    -   fix: improve panic management
    -   fix: the combination of --fix and --path-prefix

### [`v1.52.0`](https://togithub.com/golangci/golangci-lint/blob/HEAD/CHANGELOG.md#v1520)

[Compare Source](https://togithub.com/golangci/golangci-lint/compare/v1.51.2...v1.52.0)

1.  updated linters
    -   `asciicheck`: from 0.1.1 to 0.2.0
    -   `bidichk`: from 0.2.3 to 0.2.4
    -   `contextcheck`: from 1.1.3 to 1.1.4
    -   `dupword`: from 0.0.9 to 0.0.11
    -   `durationcheck`: from 0.0.9 to 0.0.10
    -   `errchkjson`: from 0.3.0 to 0.3.1
    -   `errname`: from 0.1.7 to 0.1.9
    -   `forbidigo`: from 1.4.0 to 1.5.1
    -   `gci`: from 0.9.1 to 0.10.1
    -   `ginkgolinter`: from 0.8.1 to 0.9.0
    -   `go-critic`: from 0.6.7 to 0.7.0
    -   `go-errorlint`: from 1.1.0  to 1.4.0
    -   `godox`: bump to HEAD
    -   `lll`: skip go command
    -   `loggercheck`: from 0.9.3 to 0.9.4
    -   `musttag`: from 0.4.5 to 0.5.0
    -   `nilnil`: from 0.1.1 to 0.1.3
    -   `noctx`: from 0.0.1 to 0.0.2
    -   `revive`: from 1.2.5 to 1.3.1
    -   `rowserrcheck`: remove limitation related to generics support
    -   `staticcheck`: from 0.4.2 to 0.4.3
    -   `testpackage`: from 1.1.0 to 1.1.1
    -   `tparallel`: from 0.2.1 to 0.3.0
    -   `wastedassign`: remove limitation related to generics support
    -   `wrapcheck`: from 2.8.0 to 2.8.1
2.  misc.
    -   Add TeamCity output format
    -   Consider path prefix when matching path patterns
    -   Add Go version to version information
3.  Documentation
    -   Add Tekton in Trusted By page
    -   Clarify that custom linters are not enabled by default
    -   Remove description for deprecated "go" option

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "before 3am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xNTQuMCIsInVwZGF0ZWRJblZlciI6IjM0LjE1NC4wIn0=-->

While using `transformers.WithPrimaryKeys` option there is an odd behavior being observed, where the unwrapped struct field also gets promoted to be PK.

Consider the following example:
```
type A struct {
  ID string
  B B
}

type B struct {
  ID string
}
```

Currently, if `transformers.WithPrimaryKeys("ID")` option was used to transform struct `A` we would get the following columns:
* `id`: PK, taken from `A`
* `b_id`: PK, taken from `B`

However, with the current change, the following becomes possible:

| `transformers.WithPrimaryKeys` | `id` is PK | `b_id` is PK |
| --- | --- | --- |
| `"ID"` |  `true` | `false` |
| `"B.ID"` |  `false` | `true` |
| `"ID", "B.ID"` |  `true` | `true` |

🤖 I have created a release *beep* *boop*
---


## [1.44.1](v1.44.0...v1.44.1) (2023-03-31)


### Bug Fixes

* **transform:** Use path instead of field name for PK options ([#739](#739)) ([d7649d8](d7649d8))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).