Fix checking for cell renderer function for table tab navigation

[paustint]

Teh actions column and a column with an Id have special behavior and when built the function name changes, so we attached the name to the prototype to gain access to the original name to detect when to have special behavior

[Copilot]

Pull Request Overview

This PR fixes the detection of specific cell renderer functions (IdLinkRenderer and ActionRenderer) for handling special keyboard navigation behavior in data tables. The issue was that minification/bundling changes function names, breaking the name-based detection.

• Changed from checking args.column.renderCell?.name to args.column.renderCell?.prototype?.displayName
• Added prototype.displayName properties to both IdLinkRenderer and ActionRenderer functions

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
libs/ui/src/lib/data-table/useDataTable.tsx	Updated renderer detection logic to use prototype.displayName instead of function.name
libs/ui/src/lib/data-table/DataTableRenderers.tsx	Added prototype.displayName properties to IdLinkRenderer and ActionRenderer

[Copilot]

Assigning to a function's prototype property can override its existing prototype chain. Consider using a safer approach like adding a static property (IdLinkRenderer.displayName = 'IdLinkRenderer') or using a symbol/WeakMap for function identification.

Suggested change

	IdLinkRenderer.prototype = {
	displayName: 'IdLinkRenderer',
	};
	IdLinkRenderer.displayName = 'IdLinkRenderer';

[Copilot]

Assigning to a function's prototype property can override its existing prototype chain. Consider using a safer approach like adding a static property (ActionRenderer.displayName = 'ActionRenderer') or using a symbol/WeakMap for function identification.

Suggested change

	ActionRenderer.prototype = {
	displayName: 'ActionRenderer',
	};
	ActionRenderer.displayName = 'ActionRenderer';

[Copilot]

[nitpick] The nested optional chaining with prototype access is fragile. If the prototype approach changes, consider using a more robust identification method like a static property or instanceof checks.