Thoughts on marking DenyListedApiDetector & DenyListedEntry as public?

[erawhctim]

It'd be great to be able to mix-n-match between library-owned/community denylist entries and project-private ones that we write for ourselves. We'd need a way for the detector to accept additional DenyListedEntry instances that our project could pass in, or something to that effect.

We've forked this lint check as a workaround and just maintain an internal copy of it (thank you for open-sourcing this! 🙏), but when we do that, we lose out on any updates that are pushed to the denylist in the future unless we actively merge upstream changes back into our fork.

I'm curious if there's additional consideration that's motivating keeping the denylist detector & entry class internal that I might be missing?