Add Automated Security Dependency Scanning

[Menjay7]

Summary

This PR introduces automated security dependency scanning to proactively detect vulnerable, outdated, or insecure third-party dependencies during development and CI/CD. It helps identify security risks early and prevents vulnerable packages from being deployed.

Changes Made
Added automated dependency vulnerability scanning to the CI/CD pipeline.
Configured scheduled security scans for continuous monitoring.
Enabled scanning on pull requests and pushes to protected branches.
Added severity-based reporting for Critical, High, Medium, and Low vulnerabilities.
Configured build failure thresholds for high-severity vulnerabilities.
Added support for dependency update alerts.
Improved reporting with detailed vulnerability information and remediation guidance.
Added ignore/suppression configuration for approved exceptions with expiration support.
Updated project documentation with dependency scanning setup and maintenance procedures.
Benefits
Detects vulnerable dependencies before deployment.
Improves application security posture.
Reduces the risk of supply chain attacks.
Provides continuous monitoring for newly disclosed vulnerabilities.
Encourages timely dependency updates and security best practices.
Integrates seamlessly into existing development workflows.
Testing
Verified dependency scans execute successfully in CI.
Confirmed vulnerabilities are correctly identified and reported.
Tested severity thresholds trigger expected pipeline behavior.
Validated suppression rules for approved exceptions.
Verified scheduled scans execute as expected.
Confirmed reports are generated and accessible after each scan.
Checklist
Automated dependency scanning configured
CI/CD integration completed
Severity-based reporting enabled
Build failure thresholds configured
Scheduled security scans added
Exception handling documented
Documentation updated
Tests completed successfully..closed #227

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.