Migrate nevergrad optimizers to new documentation style

[gauravmanmode]

PR Description

This PR updates the documentation of the recently added optimizers from the nevergrad library to follow the new documentation style.

Additional changes

Clarify dependancy conflict between nevergrad and bayes_opt
Closes #627
Use tab-set directive instead of tabbed
Closes #628
Also, use from __future__ import annotations in nevergrad_optimizers.py for stringified annotations.

[janosg]

@gauravmanmode can you update this branch and fix the merge conflicts?

[gauravmanmode]

Sure, I have a few things left to do here and then I will fix the merge conflicts

[codecov]

Codecov Report

❌ Patch coverage is 99.41860% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/optimagic/optimizers/nevergrad_optimizers.py	99.26%	1 Missing ⚠️

Files with missing lines	Coverage Δ
src/optimagic/algorithms.py	88.18% <100.00%> (ø)
src/optimagic/config.py	100.00% <100.00%> (ø)
src/optimagic/optimizers/bayesian_optimizer.py	91.59% <100.00%> (ø)
src/optimagic/optimizers/nevergrad_optimizers.py	77.08% <99.26%> (+10.52%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gauravmanmode]

@janosg, I have fixed the merge conflicts.

[janosg]

Very nice. Just minor comments.

[gauravmanmode]

For documenting several optimizers in here.
I am thinking of having an enum Portfolio so that choice can be made in autocomplete where description is visible for each.
Could be used as always

import optimagic as om
om.minimize(
    ...
    algorithm=om.algos.nevergrad_portfolio(optimizer="Carola2")
)

or another way

import optimagic as om
 from optimagic.optimizers.nevergrad_optimizers import Portfolio
om.minimize(
    ...
    algorithm=om.algos.nevergrad_portfolio(optimizer=Portfolio.Carola2)
)

which would look like this
Should I proceed with this ?