[Snyk] Upgrade postcss from 8.4.38 to 8.4.47

[nerdy-tech-com-gitub]

Snyk has created this PR to upgrade postcss from 8.4.38 to 8.4.47.

ℹ️ 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 9 versions ahead of your current version.

• The recommended version was released on 2 months ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	417	Proof of Concept

Release notes

Package name: postcss

• 8.4.47 - 2024-09-14
  
  • Removed debug code.
• 8.4.46 - 2024-09-14
  
  • Fixed Cannot read properties of undefined (reading 'before').
• 8.4.45 - 2024-09-04
  
  • Removed unnecessary fix which could lead to infinite loop.
• 8.4.44 - 2024-09-02
  
  • Another way to fix markClean is not a function error.
• 8.4.43 - 2024-09-01
  
  • Fixed markClean is not a function error.
• 8.4.42 - 2024-08-31
  
  • Fixed CSS syntax error on long minified files (by @ varpstar).
• 8.4.41 - 2024-08-05
  
  • Fixed types (by @ nex3 and @ querkmachine).
  • Cleaned up RegExps (by @ bluwy).
• 8.4.40 - 2024-07-24
  
  • Moved to getter/setter in nodes types to help Sass team (by @ nex3).
• 8.4.39 - 2024-06-29
  
  • Fixed CssSyntaxError types (by @ romainmenke).
• 8.4.38 - 2024-03-20
  
  • Fixed endIndex: 0 in errors and warnings (by @ romainmenke).

from postcss 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.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

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

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[trag-bot]

@trag-bot didn't find any issues in the code! ✅✨

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.

[trag-bot]

prBody:

1. Updated the version of the postcss package from 8.4.38 to 8.4.47 in the package.json file.
2. This change ensures compatibility with the latest features and fixes provided in the new version of postcss.
3. The update may address known issues or vulnerabilities present in the previous version.
4. It aligns the project dependencies with the latest stable releases, promoting better integration with other tools.
5. The change is part of routine maintenance to keep the project dependencies up to date.
6. No breaking changes are expected from this update, as it is a minor version increment.
7. The updated version will be reflected in the next build and deployment cycle.
8. This change has been tested locally to ensure that existing functionality remains intact.
9. Documentation regarding the updated version can be referenced for any new features or changes.
10. This update is a step towards maintaining a healthy and secure codebase.