Metadata editor / validation report improvements

[josegar74]

• Update buttons to display success and errors to use text instead of an icon.
• Show separate messages for success and errors.

• Add style to display the display buttons greyed when the related rules are not displayed.

• If not success or errors reported don't show the expander to display the results in the validation rules.

• Group the success and error messages.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[MichelGabriel]

@josegar74 It looks good, more clear and simple.

One thing I noticed, the expander was still there, although there were no errors.

[josegar74]

Thanks @MichelGabriel I'll check to fix that

[josegar74]

@MichelGabriel I've pushed a change to fix the expander and also improve the a bit the layout of the error / success messages and the tooltips for the buttons to hide / show the messages:

[MichelGabriel]

The expander is now hidden when there are no messages, and the rest is tested and works fine. Thanks.

[geonetworkbuild]

The backport to 4.2.x failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 2323b0a890... Metadata editor / validation report improvements:
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config advice.mergeConflict false"

stdout

Auto-merging web-ui/src/main/resources/catalog/locales/en-editor.json
CONFLICT (content): Merge conflict in web-ui/src/main/resources/catalog/locales/en-editor.json
Auto-merging web-ui/src/main/resources/catalog/style/gn_editor.less

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.2.x 4.2.x
# Navigate to the new working tree
cd .worktrees/backport-4.2.x
# Create a new branch
git switch --create backport-8395-to-4.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 2323b0a89084241f901e8f71357b4ba8f79b8322,9b12031edb7e38c42830d25bfdbdb105e4eb5f5d
# Push it to GitHub
git push --set-upstream origin backport-8395-to-4.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.2.x

Then, create a pull request where the base branch is 4.2.x and the compare/head branch is backport-8395-to-4.2.x.