chore(fp): use more conservative CPE 22 prefix suppression syntax to avoid false negatives

[chadlwilson]

Description of Change

CPE 2.2 URI suppressions are string prefix based off a fully formed URI; without the colon we risk matching against the wrong product, sometimes sub-products.

DependencyCheck/core/src/main/java/org/owasp/dependencycheck/xml/suppression/SuppressionRule.java

Lines 778 to 786 in c82a59c

	final String id;
	try {
	id = cpeId.toCpe22Uri().toLowerCase();
	} catch (CpeEncodingException ex) {
	LOGGER.debug("Unable to convert CPE to 22 URI?" + cpeId);
	return false;
	}
	final String check = suppressionEntry.getValue().toLowerCase();
	return id.startsWith(check);

It's possible some of these are intentional product prefixes; but probably better to address these one-by-one if so. The current ones risk creating false negatives, especially over time as new sub-products are added.

Related issues

• chore(fp): convert hosted/generated suppressions to more conservative CPE prefix suppressions #8510 for the hosted/generated suppressions
• tests failing due to unrelated issue test: fix expectations for RetireJS against AngularJS integration test #8511

Have test cases been added to cover the new functionality?

N/A

[chadlwilson]

Thank for dealing with the conflicts for me, you didn't have to do that, so it's appreciated 🙏🏻