Fix #9623 widgets font customizations

[MV88]

Description

Now you can customize some properties of the font that will be stored inside layout prop or coutnerOpts

• Counter widget fontSize had been hidden because that is automatic
• Pie chart can customize the font inside the hover, but not inside the pie, because you would lose some auto corrections on the fontSize
• A new Layout tab has been added that will contain general chart layout info, but you can then override it with the values inside the x,y axes
• removed pie options chart comp since it's zombie code

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?

Fix #9623

What is the new behavior?

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

[allyoucanmap]

Overall the code is good, just few changes:

• we should remove font color on pie chart because the default behaviour is better. Bu default it uses the contrast color for each slice of the pie
• line and bar chart have the layout section for font called Popup style but it has only effect on the axis. I think the title should be different like Font. It seems there is none font options applied globally to the plolty configuration, is this intentional?
• the font family select is clearable but it we click on the x an error in console shows up
• I think the Noto font family should not be included in the list because it's not considered a web safe font and it related to the default theme of mapstore that could be different in a custom project. My proposal is to remove the Noto Sans from the list and display the Inherit label so plolty will use the page font by default

[allyoucanmap]

I don't think a useEffect is needed in this case because the current selected tab could be computed directly in the render:

const selectedTab = selectedTrace?.type === "pie" && tab === "axis" ? "traces" : (selectedTrace?.type || "traces");

then use:

{tabContents[selectedTab]}

the selectedTab can be also passed to other components as tab prop

[MV88]

are you sure about this line, especially in the false part selectedTab could be = to selectedTrace?.type which is not a tab

maybe it was tab || "traces" or simply tab?

[allyoucanmap]

yes, it was like that, I wrote the code in the comment not tested

[MV88]

Overall the code is good, just few changes:

• we should remove font color on pie chart because the default behaviour is better. Bu default it uses the contrast color for each slice of the pie

makes sense

• line and bar chart have the layout section for font called Popup style but it has only effect on the axis. I think the title should be different like Font.

yes I've missed it during refactor

It seems there is none font options applied globally to the plotly configuration, is this intentional?

what do you mean exactly by "globally"?
In the Layout tab you can configure generic font attributes that are applied to all traces in that specific chart

• the font family select is clearable but it we click on the x an error in console shows up

I'll remove clearable

• I think the Noto font family should not be included in the list because it's not considered a web safe font and it related to the default theme of mapstore that could be different in a custom project. My proposal is to remove the Noto Sans from the list and display the Inherit label so plotly will use the page font by default

sounds good

[MV88]

@allyoucanmap
PR is ready again for review

[allyoucanmap]

@ElenaGallo please test this fix on dev, thanks