Fix: Table not keeping focused cell visible

[filipbalucha]

Fixes #1609

Checklist

• [ ] Includes tests
• [ ] Update documentation

Changes proposed in this pull request:

• Make sure the focused cell is visible on click or keyboard navigation (including when controlled via props)
• Improve internal docs
• Add pointers for other improvements uncovered as part of the work here (see end of PR)

Reviewers should focus on:

Screenshot

Before:

https://github.com/palantir/blueprint/assets/40673216/fef9d318-f6da-46d2-9032-d0248940d2fe

After:

https://github.com/palantir/blueprint/assets/40673216/322ce3ec-afee-4abe-8839-3f9db9b13318

Not addressed in this PR

• Polishing interactions with frozen cells. The scrollable part of the table should only scroll if the frozen cell would otherwise not be visible. This is not a regression caused by this PR; rather, it is a logical next step.

  https://github.com/palantir/blueprint/assets/40673216/1a637d89-9d2a-4f01-b509-fae83533a3d4

• getColumnIndicesInRect operates on viewport rect but does not ignore headers or take frozen cells into account; this might be feeding into https://github.com/palantir/blueprint/issues/4780 and potentially contaminating the response of onVisibleCellsChange. Again, this is a side observation rather than a regression.

[palantirtech]

Thanks for your interest in palantir/blueprint, @filipbalucha! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

[changelog-app[bot]]

Generate changelog in changelog-dir>`packages/table/changelog/@unreleased`</changelog-dir

What do the change types mean?

- `feature`: A new feature of the service. - `improvement`: An incremental improvement in the functionality or operation of the service. - `fix`: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way. - `break`: Has the potential to break consumers of this service's API, inclusive of both Palantir services and external consumers of the service's API (e.g. customer-written software or integrations). - `deprecation`: Advertises the intention to remove service functionality without any change to the operation of the service itself. - `manualTask`: Requires the possibility of manual intervention (running a script, eyeballing configuration, performing database surgery, ...) at the time of upgrade for it to succeed. - `migration`: A fully automatic upgrade migration task with no engineer input required. _Note: only one type should be chosen._

How are new versions calculated?

- ❗The `break` and `manual task` changelog types will result in a major release! - 🐛 The `fix` changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease. - ✨ All others will result in a minor version release.

Type

- [ ] Feature - [ ] Improvement - [ ] Fix - [ ] Break - [ ] Deprecation - [ ] Manual task - [ ] Migration

Description

Fb/fix table does not keep focused cell in viewport **Check the box to generate changelog(s)** - [ ] Generate changelog entry