SO Management: revert incorrect sorting on tags column

[pgayvallet]

Summary

Fix #138591

In short: Fix the incorrect sorting that was added to the SOM table's tags column in #132525

In long: The GetTableColumnDefinition tagging API returns a column definition that is sortable by default. However this sorting logic only works for browser-side paginations:

kibana/x-pack/plugins/saved_objects_tagging/public/ui_api/get_table_column_definition.tsx

Lines 37 to 43 in 6cfbb2f

	sortable: serverPaging
	? false
	: (object: SavedObject) => {
	const { tags } = getTagsFromReferences(object.references, cache.getState());
	tags.sort(byNameTagSorter);
	return tags.length ? tags[0].name : undefined;
	},

#132525 added sorting to the SOM table, and, by doing that, enabled the sorting capability for the tags column. However when performing server-side paging, the sortable logic of the column is just ignored, and the value of the column just sent to the server.

Add to that that this tags column cannot be converted to a proper ES sort term, and we're forced to set the tags column back to non-sortable, which is what this PR does.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 878a434

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
savedObjectsTaggingOss	46	47	+1

Async chunks

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

id	before	after	diff
savedObjectsManagement	83.8KB	83.8KB	+17.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
savedObjectsTagging	17.9KB	17.9KB	+28.0B

Unknown metric groups

API count

id	before	after	diff
savedObjectsTaggingOss	91	94	+3

History

• 💚 Build #69311 succeeded f3c4cec

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

[afharo]

LGTM

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.4

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation