Static web features catch-up to Qt

[oharboe]

Please pick whatever is useful here for the static web GUI and close this PR.

To test new features, run:

bazelisk run test/orfs/gcd:gcd_synth_html

• Click above the green bucket and you can still go to the timing report for that bucket
• Pin inspector

- Sortable columns

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[gemini-code-assist]

Code Review

This pull request enhances the web-based timing report by adding a Pin Inspector popover, implementing table sorting for paths and details, and improving histogram hit detection. It also updates the Bazel build configuration to handle ORFS and Yosys overrides at the root and transitions to local ASAP7 files for testing. Feedback addressed critical issues regarding index mismatches in sorted tables, potential memory leaks in event listener management, and incorrect comparison logic for identical missing values during sorting.

[oharboe]

/gemini review

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"

[gemini-code-assist]

Code Review

This pull request enhances the web-based timing report and chart widgets, introducing sortable tables for timing paths and details, a new 'Pin Inspector' popover for deep-diving into node properties, and improved hit-testing for histogram interactions. Additionally, it updates Bazel dependencies for the ORFS integration, replacing Docker-based file references with local overrides and patches to improve build hermeticity. Review feedback identifies a logic error in the value comparator that violates the comparator contract for missing values and suggests preserving the selection state when the detail table is re-sorted.

[gemini-code-assist]

The _selectedDetailIndex is not updated when the detail table is re-sorted. This will cause the selection highlight to point to the wrong row after a sort operation. Consider tracking the selected node by identity and updating the index, similar to how _selectedPathIndex is handled in _renderPathTable.

        const selectedNode = this._selectedDetailIndex >= 0 ? nodesSrc[this._selectedDetailIndex] : null;
        const nodes = this._detailSort
            ? sortRowsInPlace([...nodesSrc], this._detailSort)
            : nodesSrc;
        if (selectedNode) {
            this._selectedDetailIndex = nodes.indexOf(selectedNode);
        }

[gemini-code-assist]

The compareValues function has an inconsistent comparison logic for missing values (null, undefined, or empty string). If a is null and b is undefined, it returns 1. If a is undefined and b is null, it also returns 1. This violates the contract of a comparator where compare(a, b) should be the negative of compare(b, a). It should first check if both values are missing.

Suggested change

	export function compareValues(a, b, dir) {
	if (a === b) return 0;
	const mul = dir === 'desc' ? -1 : 1;
	const na = typeof a === 'number';
	const nb = typeof b === 'number';
	if (na && nb) return (a - b) * mul;
	// Missing values sort last regardless of direction.
	if (a === undefined || a === null || a === '') return 1;
	if (b === undefined || b === null || b === '') return -1;
	return String(a).localeCompare(String(b)) * mul;
	}
	export function compareValues(a, b, dir) {
	if (a === b) return 0;
	const isMissing = (v) => v === undefined || v === null || v === '';
	if (isMissing(a) && isMissing(b)) return 0;
	if (isMissing(a)) return 1;
	if (isMissing(b)) return -1;
	const mul = dir === 'desc' ? -1 : 1;
	const na = typeof a === 'number';
	const nb = typeof b === 'number';
	if (na && nb) return (a - b) * mul;
	return String(a).localeCompare(String(b)) * mul;
	}

[github-actions]

clang-tidy review says "All clean, LGTM! 👍"