[Lens] Fix axis title visibility bug

[dej611]

Summary

Fixes #133516

This PR addresses the inconsistency issue with axis title visibility: the bug was due to the classic redux double state update, where the second update was overriding the first state update.
In the specific case the title update was overriding the visibility one, leading to the bug.

The PR refactors the update function to be unique and update both values at once.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: cc5b82a
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
expressionXY	96.5KB	96.5KB	-5.0B
lens	1.2MB	1.2MB	+108.0B
total			+103.0B

History

• 💔 Build #50207 failed dcaf4ef

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[flash1293]

Great catch! LGTM

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	8.3	Backport failed because of merge conflicts You might need to backport the following PRs to 8.3: - [XY] showTooltip argument. (#130530)

Manual backport

To create the backport manually run:

node scripts/backport --pr 134082

Questions ?

Please refer to the Backport tool documentation