Replace lifecycle functions with UNSAFE_ versions

[jna4k]

Description

This PR replaces componentWillReceiveProps and componentWillUpdate with the UNSAFE_componentWillReceiveProps and UNSAFE_componentWillUpdate lifecycle functions.

This change is necessary is to make sure that our legacy components will work with react 17+ see https://legacy.reactjs.org/blog/2018/03/27/update-on-async-rendering.html

This change was done as a part of the React 19 upgrade, see #12500

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Other... Please describe:

Issue

What is the current behavior?

#12500
We are currently using the componentWillReceiveProps and componentWillUpdate lifecycle functions.

What is the new behavior?

We will no longer use the componentWillReceiveProps and componentWillUpdate lifecycle functions, and will instead us.e the UNSAFE_componentWillReceiveProps and UNSAFE_componentWillUpdate versions that are compatible with react 17+

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[tdipisa]

@jna4k thank you for opening that. PSC members will check the issue definition and this asap.