[chore] Ignore vulnerability in DependencyCheck and bumped the version

[nwithan8]

Description

The DependencyCheck plugin we use to scan for vulnerabilities in our library is, itself, vulnerable. This is a red herring that unfortunately causes our CI to fail.

This PR will ignore this known vulnerability for the time being.

This does NOT pass vulnerable code down to our end-users, as this is purely an issue with one of the plugins we use to test the library.

Testing

• make scan calls dependency check as expected
• Dependency scan passes as expected (no current vulnerabilities other than the aforementioned vulnerability inside the now-removed Maven plugin)

Pull Request Type

Please select the option(s) that are relevant to this PR.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement (fixing a typo, updating readme, renaming a variable name, etc)

[dcaballeroc]

Still failing with Github Actions though

[Justintime50]

I don't love this particular solution. Let's chat internally about this. I feel it defeats the point of having a dependency manager if we just store local copies of the dependencies. Dependencies typically shouldn't be checked into a repo if we can help it since it's not our code and will make future diffs bigger than they should be.

[dcaballeroc]

Looks in line with what Justin was asking

Addressed