[FEA] allow tighter explicit cudf artifact dependency configuration

[gerashegalov]

Is your feature request related to a problem? Please describe.
As a RAPIDS Spark Plugin developer working across cuDF and spark-rapids I wish I could more robustly point to a cudf build dependency without fearing of non-deterministically pulling the cuDF artifact from a remote build instead of the locally-built test artifact. Developers often report bugs or successful tests that cannot be confirmed in CI

Describe the solution you'd like
Have an easy explicit flag/profile that deterministically switch between locally-built cudf artifact and remote artifacts. E.g. -Dcudf.home=/local/path/to/cudfrepo

We may also change local cuDF automation like rapidsai/cudf#10578 produce a version suffix or dedicated classifier -local, and override dependency version via simple Profile switch like -PlocalCudf

Describe alternatives you've considered
carefully inspect the log file and verify the build info

Additional context
N/A