Reduce false positives in privacy policy check

[rbowen]

Problem: The privacy policy site check flags 17 projects as non-compliant even though they link to valid privacy policy pages hosted on their own *.apache.org subdomain. This is a 89% false positive rate for this check.

Fix: Expand the CHECK_VALIDATE regex to also accept any URL on *.apache.org that contains "privac" in the path.

Projects that will move from WARN → PASS: beam, bookkeeper, bval, helix, hudi, johnzon, karaf, knox, openjpa, opennlp, pig, shiro, systemds, tomee, uima, unomi, zookeeper

Still correctly rejected: policies.google.com/privacy (parquet), github.com/apache/privacy-website (dataprivacy)

Many projects host their own privacy policy page on their *.apache.org subdomain (e.g., beam.apache.org/privacy_policy, karaf.apache.org/privacy.html). These pages typically mirror or link to the canonical ASF privacy policy, but are currently flagged as non-compliant because the validation regex only accepts two exact canonical URLs.

This change adds a third alternative that accepts any *.apache.org URL containing 'privac' (covering privacy, privacy-policy, privacypolicy, etc.).

This eliminates 17 of 19 privacy warnings as false positives while still correctly rejecting links to non-ASF domains (e.g., policies.google.com).

Also adds rspec tests for the privacy check.

[sebbASF]

-1

According to https://www.apache.org/foundation/marks/pmcs.html#navigation, projects must link to the privacy website. There is no option for alternatives. Whimsy needs to follow the policy.

[sebbASF]

Or the policy needs to be changed

[rbowen]

Noted.