chore: update taiga-ui config-tools to v0.229.0 - autoclosed

[taiga-family-bot]

This PR contains the following updates:

Package	Type	Change
@taiga-ui/auto-changelog-config	devDependencies	0.222.4 -> 0.229.0
@taiga-ui/browserslist-config	devDependencies	0.222.4 -> 0.229.0
@taiga-ui/commitlint-config	devDependencies	0.222.4 -> 0.229.0
@​taiga-ui/eslint-plugin-experience	devDependencies	0.222.4 -> 0.229.0
@taiga-ui/prettier-config	devDependencies	0.222.4 -> 0.229.0
@taiga-ui/release-it-config	devDependencies	0.222.4 -> 0.229.0
@taiga-ui/stylelint-config	devDependencies	0.222.4 -> 0.229.0
@taiga-ui/syncer	devDependencies	0.222.4 -> 0.229.0
@taiga-ui/tsconfig	devDependencies	0.222.4 -> 0.229.0

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[taiga-family-bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: @release-it/[email protected]
npm error node_modules/@release-it/conventional-changelog
npm error   dev @release-it/conventional-changelog@"8.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @release-it/conventional-changelog@"9.0.2" from @taiga-ui/[email protected]
npm error node_modules/@taiga-ui/release-it-config
npm error   dev @taiga-ui/release-it-config@"0.229.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /home/runner/.npm/_logs/2024-11-01T07_34_18_940Z-eresolve-report.txt
npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2024-11-01T07_34_18_940Z-debug-0.log