dbeaver/pro#4898 migrate driver properties to data grid table

[devnaumov]

closes 4898

PR replaces the old driver properties list with a virtualized DataGrid.

The DataGrid cell API now provides tabIndex as the third callback argument. react-data-grid already calculates this value for interactive controls, but our wrapper did not expose it. Passing it to inputs, comboboxes, and buttons makes keyboard navigation work correctly.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 91 complexity

Metric	Results
Complexity	91

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sergeyteleshev]

we can remove this useEffect, and do something like this:

const [propertyIdToFocus, setPropertyIdToFocus] = useState<string | null>(null);

const focusPropertyInput = useCallback((input: HTMLInputElement | null) => {
  if (input) {
    input.focus();
    setPropertyIdToFocus(null);
  }
}, []);

<DriverPropertyNameCell
  property={property}
  error={!isKeyUnique(property.key)}
  readOnly={readOnly}
  inputRef={property.id === propertyIdToFocus ? focusPropertyInput : undefined}
  tabIndex={tabIndex}
  onChange={changeName}
/>