[Snyk] Upgrade jspdf-autotable from 3.8.2 to 3.8.3

[snipe]

Snyk has created this PR to upgrade jspdf-autotable from 3.8.2 to 3.8.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 1 version ahead of your current version.

• The recommended version was released on 21 days ago.

Release notes

Package name: jspdf-autotable

• 3.8.3 - 2024-08-30
  

  Remove console log

• 3.8.2 - 2024-02-12
  

  What's Changed

  • Handle tables without thead gracefully by @ ihorbond in #1034

  New Contributors

  • @ ihorbond made their first contribution in #1034

  Full Changelog: v3.8.1...v3.8.2

from jspdf-autotable GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[what-the-diff]

PR Summary

• Project Name Update
  The name of the project has been updated from "snipe-it" to "relock-npm-lock-v2-6yW7J5" in the package-lock.json file. This does not affect the functionality but helps to manage and distinguish different versions of our project.

• Package Update
  The version of jspdf-autotable, a package that is used for automatically creating tables in the PDF files, has been updated from ^3.8.2 to ^3.8.3. This update is reflected in both package-lock.json and package.json files. Newer version usually come with improved functionality and bug fixes.

• Metadata Update for a Package
  The package metadata for jspdf-autotable in package-lock.json has been updated. This includes the new version number, the URL where the package can be found, and the integrity hash which is a type of digital 'fingerprint' for verifying the package contents. This ensures that we're using the correct and secure version of this package.