Infra/Client-Runs: User-added Table Columns Don't Persist

[ChefAustin]

Describe the bug

After adding additional columns (i.e. Client Version, Deprecations) to node table on /infrastructure/client-runs view if one then refreshes the page the newly added columns do not persist.

To Reproduce

Steps to reproduce the behavior:

• Login to AutomateUI (in my case, this is a SAML-authenticated session)
• Navigate to Infrastructure > Client Runs view from top navbar
• Select ⚙️ icon to drop-down the available table columns
• Add Client Version column to table
• Refresh the page
• The newly added Client Version column is no longer displayed

This can also be reproduced in a similar -- but slightly different -- way:

• Login to AutomateUI (in my case, this is a SAML-authenticated session)
• Navigate to Infrastructure > Client Runs view from top navbar
• Select ⚙️ icon to drop-down the available table columns
• Add Client Version column to table
• Select user icon from the top-right-hand corner of the page
• Click 'Sign Out' from drop-down list
• Re-login to AutomateUI (in my case, this is a SAML-authenticated session)
• Navigate to Infrastructure > Client Runs view from top navbar
• The newly added Client Version column is no longer displayed

Expected behavior

1. Refreshing the infrastructure/client-runs page after adding new column(s) to the Client Runs table should not result in those the existence of those additional columns.
2. Logging out/in to AutomateUI should not affect the existence of those additional columns.

Screenshots

If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: macOS 11.4 (20F71)
• Browser: Google Chrome Version 91.0.4472.77 (Official Build) (x86_64)
• Automate Build Number: 20210504113343

Additional context

I think it would ideal for the display settings to be persisted somewhere so that the chosen table display configurations are used for the entire life of the user (in other words, these settings should persist beyond a single page rendering and even beyond a user session). At the very least, I think they should "stick" for the lifetime of the user session.

Aha! Link: https://chef.aha.io/epics/SH-E-651