docs: document the (weak) random value situation in rustls builds

[bagder]

No description provided.

[ctz]

We will address this.

[cpu]

Would you be open to tagging a Rustls dev when you bump into these sorts of issues? I hate to make more work for the curl folks but this sort of thing can fly under the radar otherwise. I spotted it by chance when looking at git log while curious about another topic. The curl repo is tricky to set a global watch on because y'all are too productive 😆

[bagder]

@cpu sure, if you have any preference for who/how to tag you, I could certainly make an effort to!

[cpu]

any preference for who/how to tag you

You can definitely tag me liberally. I'll let ctz decide himself if he wants the notifications :-)

Beyond bugs/issues I'm also happy to give non-blocking reviews on Rustls-related PRs like #14535 It's helpful to see where our APIs might be awkward/underdocumented.

[ctz]

Please do tag me too.

[cpu]

We landed a capability for this upstream in the yet-to-be-released rustls-ffi 0.14. I will pick up a fix for the curl side along with an update for the relevant breaking changes once we cut a release. Thanks!