Implementation of backend plotting for profile_plot

[r3kste]

This PR refactors profile_plot() to use the backend plotting module.

Backends

Plotly	Matplotlib

Plot Changes

• A line is drawn at y=1. The color and linewidth of the line matches that of the axis.

Before	After

PR Checklist

• Compared images before and after making changes
• Changes made are tested.
• Update Documentation.

[codecov]

Codecov Report

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

Files with missing lines	Patch %	Lines
src/optimagic/visualization/profile_plot.py	96.29%	1 Missing ⚠️

Files with missing lines	Coverage Δ
src/optimagic/visualization/backends.py	97.91% <100.00%> (+0.24%)	⬆️
src/optimagic/visualization/profile_plot.py	91.52% <96.29%> (+0.61%)	⬆️

🚀 New features to boost your workflow:

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

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[r3kste]

Ping @timmens for review. I have made the suggested changes.

[timmens]

Very very nice!

I have a few questions / requested changes.

[timmens]

Very nice. Approved!

I only have a tiny comment. You can merge the PR after fixing that.

[r3kste]

Thanks for merging!

Information about Tidy Dataframe:

As per the previous implementation, the solution_times DataFrame returned by create_solution_times is tidy. This approach was introduced to simplify plotting with seaborn.

With the new backend plotting system, a tidy DataFrame is no longer required. Therefore, the data extraction logic could potentially be simplified. Unfortunately, I couldn't find a way to do this without effectively performing the same operations required to tidy the DataFrame, which therefore, might not provide any significant improvement in terms of complexity.