feat(table): expand cell harness api - #21162

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

@googlebot I signed it!

The changes are fine, but for some reason the CI didn't run on your PR. If it did, I'm pretty sure that it would've failed, because the API goldens need to be updated too. You can update them using yarn approve-api table/testing.

@josephperrott do you know why the CI didn't run here?

@crisbeto Thanks for your feedback. I resolved the comments with a new commit.

It doesn't look like the CI checks ran this time around either.

@crisbeto Is there anything I can do about that?

I've heard that this can happen if somehow Circle CI is enabled on your fork so that might be something worth checking.

I looked into it and am unsure of why CircleCI did not run as expected in this case. I have manually triggered our CI run.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}