make cuCat opt-in

[lmeyerov]

To help mitigate risk, let's make cuCat opt-in

What should the interface be?

• should work clearly with other opts
• should work clearly with implicit featurize calls like .umap()
• when we flip default to on, e.g., engine=cudf, should not be too painful to change

[dcolinmorgan]

i have added 'cucat' flag within feature_engine under cucat branch, so opt-in use case is set once installed from pip graphistry/cucat

[lmeyerov]

great, see my comments on the branch

[dcolinmorgan]

lingering torch_check question https://graphistry.slack.com/archives/C0487PGP96E/p1677633106428139

[lmeyerov]

including in issues we can close now/soon (?)

[dcolinmorgan]

the umap and feautize flags work well and independently. I believe this fulfills opt-in bullets at top

easy to swap in cu_cat down the road as default

[lmeyerov]

great let's close when https://github.com/graphistry/pygraphistry/pull/486 is ready to merge ! (see comments there)