Fix/update domains table style

[roo2]

Fixes most of 7169-gh-Automattic/dotcom-forge

We can make these two tables more consistent:
Add hover state to the domains table.

Table headers are the same for both tables (Font sizes, color, etc).

This PR tidies up padding, alignment and heights so that the domains table matches the sites table on all resolutions. I also tidied up alignment of the sites table header.

before:

after:

Sites table header:

before:

after:

Note: I haven't dealt with table widths on the domains table, because it has quite a complex display method that is different from the sites table, we can work on that in another PR

Testing instructions

Ensure that /domains/manage and /sites table headers are similar at all resolutions.

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-108176

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-108176&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-108176&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~42 bytes added 📈 [gzipped])

name     parsed_size           gzip_size
domains       +278 B  (+0.0%)      +42 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[roo2]

If anyone is testing this, here a trick to check that the paddings match between the /sites page and the /domains/manage page in chrome:

Open /sites page in one tab
Open /domains/manage in another tab.
Open dev tools in tab#1, choose a size.
In tab#2, close the dev tools, then re-open them. This will cause the dev tools to be sized the same in both tabs.
flick back and forth between the tabs, compare the pages.
Adjust dev tools in tab#1 to choose a new width.
In tab#2, close and open the dev tools again, they will get the same width as tab#1
repeat.

Just a trick that works in chrome, it also works when selecting a responsive width, it's also useful for comparing with wordpress.com.

Screen.Recording.2024-05-20.at.10.13.38.am.mov

[roo2]

oops, bad rebase here.

[roo2]

bad rebase here as well

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/update-domains-table-style on your sandbox.

[taipeicoder]

Works great 👍