Mark ES_MDA as recommended algorithm

[berland]

Issue
Resolves #9739'

Approach
Modify description(), and use a newline character to get formatting right. This newline might look bad elsewhere if this string is in other places than the GUI

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[codspeed-hq]

CodSpeed Performance Report

Merging #9771 will improve performances by 10.48%

_{Comparing berland:rec_esmda (a8db6b0) with main (61a6776)}

Summary

⚡ 2 improvements
✅ 22 untouched benchmarks

Benchmarks breakdown

	Benchmark	main	berland:rec_esmda	Change
⚡	test_load_from_context[gen_x: 20, sum_x: 20 reals: 10]	7.1 ms	6.4 ms	+10.48%
⚡	test_direct_dark_performance_with_storage[gen_x: 20, sum_x: 20 reals: 10-gen_data-get_record_observations]	1.5 ms	1.4 ms	+10.3%

[andreas-el]

This definitely solves the issue at hand.
Question is, should we emphasise this in the title?

Multiple Data Assimilation - [Recommended]

or something similar?

[sondreso]

I would prefer having the recommended marking in the title, but I think the deprecation is fine to have in the description.

[berland]

[sondreso]

Nice ✨

[sondreso]

Could this be backported as well?

[berland]

Code has changed, re-requesting review

[berland]

Oopsie, auto-merge..