[Snyk] Fix for 2 vulnerabilities

[sidhantpanda]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Neutralization of Special Elements in Data Query Logic SNYK-JS-MONGOOSE-8446504	721
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-8482416	721

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• 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 fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Improper Neutralization of Special Elements in Data Query Logic
🦉 Regular Expression Denial of Service (ReDoS)

[github-actions]

Code review by ChatGPT

[github-actions]

1. Version Updates:

• The code patch updates the versions of "express" and "mongoose" packages. This can introduce new features, fixes, or improvements from the newer versions. It's important to review the release notes of these packages to ensure compatibility with existing code and any breaking changes.

2. Dependency Check:

• It's essential to test the code with these updated package versions to verify if it works as expected and doesn't introduce any new issues. Running unit tests, integration tests, and checking for any deprecation warnings would be beneficial.

3. Risk Assessment:

• Since this code patch involves updating critical dependencies like "express" and "mongoose," there's a risk of compatibility issues with other parts of the codebase or third-party modules. It's crucial to thoroughly test the application after the update to mitigate such risks.

4. Regular Dependency Updates:

• Regularly monitoring and updating dependencies ensure that the application stays up-to-date with security patches, performance improvements, and new features. Consider setting up automated dependency checks and notifications to streamline this process.

5. Documentation:

• Update the project's documentation to reflect the changes in dependency versions. This helps in maintaining a clear overview for future developers working on the project.

Overall, while updating package versions is essential for maintaining a healthy codebase, it's crucial to do so cautiously and comprehensively to avoid any unforeseen issues.