DataViews Templates: Auto-hide description field for list view in template dataview page

[Souptik2001]

What?

In DataViews page for template -
Auto-hide the description field when the layout is switched to "List".

Why?

Closes: #57596

As mentioned in the above issue, template descriptions can be quite long and in list layout, where the width is narrow due to the preview pannel, the layout might not look very good.
The layout does look good when description is turned off. And therefore its a good idea to auto-hide the description field when the layout is switched to "List".

How?

This PR automatically adds the description field to the hidden fields when you -

• Switch the layout to "List".
• Load the page with layout set as "List".

Testing Instructions

Please see the below screencast section or refer the steps below.

• Open site-editor.
• Go to "Templates".
• By default you will see the layout is "Grid".
• Make sure the "Description" field is visible, i.e not hidden.
• Now change the layout to "List".
• You will see as the layout field is changed to "List" the "Description" field automatically gets hidden.
• But if you want you can definitely go and manually enable the "Description" field, if you still want to see it in the "List" view. But everytime you switch to "List" view, it automatically gets hidden.
• You can also do one more test.
• Switch on the "Description" field while in the "List" layout.
• And now refresh the page.
• You will see that the "Description" fields gets again auto-hidden.

Testing Instructions for Keyboard

Screenshots or screencast

Screen.Recording.2024-05-26.at.12.mp4

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @Souptik2001.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: Souptik2001.

Co-authored-by: carolinan <poena@git.wordpress.org>
Co-authored-by: jasmussen <joen@git.wordpress.org>
Co-authored-by: jameskoster <jameskoster@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @Souptik2001! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.