Fix formatting Validation Error for Map items

[ebottacin]

Description

In the validationError Array rendered there are string and maps.
The maps Item are not rendered correctly as you cam see in the image below

I've fixed the code to render properly these items

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[glowcloud]

Thanks for the fix, I can confirm that it works.
Please take a look at my comments.

[glowcloud]

Could you change this to if (Map.isMap(e)), to use a method from Immutable?

[glowcloud]

Can you remove the spacing before the colon ${e.get("propKey")}: ${e.get("error")}?

[char0n]

Can we go for a little bit more concise way of writing this code?

errors
  .map((e) => (Map.isMap(e) ? `${e.get("propKey")} : ${e.get("error")}` : e))
  .forEach((e) => result.push(e))

[char0n]

Looks good, but we require either a unit test or e2e test to verify the code change. Would you be able to provide one?

[glowcloud]

Refactored the code and added an e2e test in #9687.

Thanks for this again, your contribution will be properly attributed.