[mixed time-series] Secondary y-axis title is disguised/misplaced

[rumbin]

The Mixed Time-Series chart type allows for configuring the title of the primary and the secondary y-axis.
However, while only the title of the primary axis is shown next to the axis, the title of the secondary one is placed at the upper end of the axis where it gets hidden by bar values and zoom controls.

How to reproduce the bug

1. Create a mixed time-series chart
2. Configure axis titles for both y-axes
3. Check the Data Zoom checkbox

Expected results

Both axes carry the titles as configured

Actual results

Only the left/primary y-axis has a title shown at the center of the axis.
The title of the right/secondary axis is misplaced at the end of the axis and thus overprinted/disquised by bar values and/or zoom controls.

Screenshots

Environment

• browser type and version: Chrome 96.0.4664.93
• superset version: 1.4.0
• all other versions: as defined in Superset's Docker image
• Feature flags:

# stable:
      "THUMBNAILS": True,
      "SQLLAB_BACKEND_PERSISTENCE": True,
      "ENABLE_TEMPLATE_PROCESSING": True,
      "DASHBOARD_CROSS_FILTERS": True,

      # experimental:
      "ALERT_REPORTS": True,
      "ALERTS_ATTACH_REPORTS": True,
      "DASHBOARD_NATIVE_FILTERS": True,

      # unclassified:
      "ENABLE_EXPLORE_DRAG_AND_DROP": True,
      "ENABLE_DND_WITH_CLICK_UX": True,

      # development:
      "DASHBOARD_NATIVE_FILTERS_SET": True

Checklist

Make sure to follow these steps before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if there are any.
• I have reproduced the issue with at least the latest released version of superset.
• I have checked the issue tracker for the same issue and I haven't found one similar.

[villebro]

Repro'd - I started working on a fix but I identified multiple inconsistencies in this area, so will need to circle back slightly later due to lack of time right now.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

[rumbin]

This issue should not be closed by the stale bot, in my eyes.

[vaibhav-malpani]

Any updates on this?
We are using mixed-time series on our dashboard.. and this issue really does not look good.