Remove dependency on conscrypt from build rules.

Bouncycastle doesn't depend on conscrypt at build time. The only
reference to conscrypt is via a reflective access to instantiate one
of its private digest classes, with a fallback to BC if the class
isn't found.

It doesn't make sense to declare this dependency because :
- BC can function normally even if this dependency doesn't exist.
- There's no guarantee that the reflective access succeeds - it's only
  guaranteed to do so if called if the caller code is present in
  the bootclasspath.

Test: make
Bug: 73635411
Change-Id: Iefa7af6a43d61a3ed4ad59c9d7b22b32a89236df
1 file changed