Update dependency ts-loader to v8.0.17

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
ts-loader	8.0.11 -> 8.0.17

---

Release Notes

TypeStrong/ts-loader

v8.0.17

Compare Source

• Included correct webpack source location in emitted errors - thanks @​lorenzodallavecchia

v8.0.16

Compare Source

• Re-Fixed missing errors in watch mode in webpack5 - thanks @​appzuka

v8.0.15

Compare Source

• Update definition files in watch mode in webpack@5 - thanks @​appzuka,@​JonWallsten,@​alexander-akait
• Add afterDeclarations to getCustomTransformers in README.md - thanks @​appzuka

v8.0.14

Compare Source

• Upgrade chalk, loader-utils, and semver to latest stable versions - thanks Avi Vahl

v8.0.13

Compare Source

• Speed up builds by adding an in-memory cache to file path lookups - thanks @​berickson1

v8.0.12

Compare Source

• Instead of checking date, check time thats more accurate to see if something has changed - thanks @​sheetalkamat

---

Renovate configuration

📅 Schedule: "every weekend" (UTC).

🚦 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.

---

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

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[renovate]

⚠️ 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 check 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 WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile