Adding a new function crypto.x509.parse_and_verify_certificates_with_options

[yogisinha]

Why the changes in this PR are needed?

parse and verify x509 certificates with additional options in package x509.crypto was requested

What are the changes in this PR?

a new builtin function was added. Following files are modified
ast/builtins.go
topdown/crypto.go
topdown/crypto_test.go
builtin_metadata.json
capabilities.json

Notes to assist PR review:

Further comments:

[netlify]

✅ Deploy Preview for openpolicyagent ready!

Name	Link
🔨 Latest commit	f0a8cb5
🔍 Latest deploy log	https://app.netlify.com/sites/openpolicyagent/deploys/66042064629c5600081694a2
😎 Deploy Preview	https://deploy-preview-6643--openpolicyagent.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[charlieegan3]

Thanks for this @yogisinha, I have tested this now myself on my machine and think we're good to go now! 🚢

Have you got a use case for this built-in where you work? Do you think we have enough docs for Rego in this area?

[yogisinha]

@charlieegan3 ,

Thanks for this @yogisinha, I have tested this now myself on my machine and think we're good to go now! 🚢

Have you got a use case for this built-in where you work? Do you think we have enough docs for Rego in this area?

No we don't have any use cases for this in our company. I think the Rego docs are good as we went through many iterations.

Just a general question. Whats the best way to maintain git hygiene when I am working on an issue.

1. Do I need to do git pull upstream main (my upstream points to opa github) every now and then to keep my branch synced up with main branch. Because whenever I do rebase, I get merge conflicts. don't know why ?
2. Any other suggestions on git hygiene.

[charlieegan3]

Hey, good question. The best thing to do is to periodically run git fetch origin && git rebase origin/main and run this on your local machine, running git rebase --continue once you have addressed any issues. Then use git push -f $BRANCH to update the contents of the remote branch of your fork. This will remove the warnings on GH, and make it easier to get changes in.