[FEA]: Add ForceAtlas2 cuGraph params

[MathisHammel]

Is this a new feature, an improvement, or a change to existing functionality?

Improvement

How would you describe the priority of this feature request

Medium

Please provide a clear description of problem this feature solves

Currently, cuGraph supports a set of parameters on ForceAtlas2 which is more complete than the default NetworkX implementation:

• mobility which was added in ForceAtlas2: continue #5213 for prevent_overlapping and mobility cugraph#5260 and ForceAtlas2 - support for prevent_overlapping and mobility cugraph#5213 (along with support for prevent_overlapping)

• barnes_hut_optimize and barnes_hut_theta, which was marked as todo here:

  nx-cugraph/nx_cugraph/drawing/layout.py

  Line 187 in b7ad703

  # We may want to expose barnes-hut--it's also surprising nx doesn't have it

This looks like a relatively minor fix and I'm already familiar with cuGraph's internals (I authored the initial PR adding mobility and prevent_overlapping) so I'm happy to handle this with my teammate @victor-lafarge.

Describe your ideal solution

Adding params mobility, barnes_hut_optimize and barnes_hut_theta to function forceatlas2_layout so that they are supported natively via NetworkX.

We are also thinking about implementing those in NetworkX to reduce the feature gap between nx and nx-cugraph, but this has lower priority.

Describe any alternatives you have considered

So far, we've been calling cuGraph directly, which works well but requires more boilerplate code

Additional context

No response

Code of Conduct

• I agree to follow nx-cugraph's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request