Feat: Support for column customization for Glossary term table

[shrushti2000]

This PR introduces enhancements to the Glossary Term table, adding support for column customization and improving the status filtering mechanism. The following features have been implemented:

1. Column Selection via Dropdown: Users can choose which columns to display in the Glossary Term table using a dropdown menu, allowing for a more customized table view.

2. Rearrangement of Columns: Users can rearrange the columns in the table by dragging and dropping them to their desired positions within the column selection dropdown.

3. Addition of Two New Columns: The Glossary Term table now includes two new columns: Synonyms and Reviewers, providing additional term-related information.

4. Fixed "Name" Column: The "Name" column is now fixed and cannot be hidden, ensuring it remains visible at all times while users customize the other columns.

5. Table-Level Status Filtering with Dropdown: The column-level filtering for status has been removed and replaced with a table-level filter. Users can now filter by status using a dropdown selection at the top of the table, making it easier to manage status-based filtering.

Feature Demo: Column Customization in Glossary

https://github.com/user-attachments/assets/c08cb8e7-f00f-414d-ac96-e0c861391aaa

Feature Demo: Table-Level Status Filtering

https://github.com/user-attachments/assets/bc37e3a4-69ec-4afa-b54a-36b1118a9184

#

Type of change:

• [ ] Bug fix
• [ ] Improvement
• [ ] New feature
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation

#

Checklist:

• [x] I have read the CONTRIBUTING document.
• [ ] My PR title is Fixes <issue-number>: <short explanation>
• [ ] I have commented on my code, particularly in hard-to-understand areas.
• [ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[github-actions[bot]]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[github-actions[bot]]

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR. You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions[bot]]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	63.56% (39261/61773)	40.14% (15548/38731)	42.24% (4665/11044)

[github-actions[bot]]

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR. You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions[bot]]

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR. You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions[bot]]

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR. You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions[bot]]

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR. You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[github-actions[bot]]

The Python checkstyle failed.

Please run make py_format and py_format_check in the root of your repository and commit the changes to this PR. You can also use pre-commit to automate the Python code formatting.

You can install the pre-commit hooks with make install_test precommit_install.

[sonarcloud[bot]]

Quality Gate passed for 'open-metadata-ui'

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud