`clearError()` call is missing `baseName` in AdSense setup component

[tofumatt]

Bug Description

The clearError() call here was not updated in #5858: https://github.com/google/site-kit-wp/blob/a84602fd1db5a2e89fe24943aae01ba29db6caf3/assets/js/modules/adsense/components/setup/SetupMain.js#L230. This means if an error was encountered during AdSense setup, and the user retries, the error will not be cleared and they'll need to do a full-page refresh.

Because of this, it isn't a show-stopping bug, though if it's straightforward would be great to get out in this release.

Steps to reproduce

1. Set up Site Kit
2. Using the tester plugin, ensure your AdSense account status is set and not set to "Ready"
3. Go to the AdSense setup page
4. Wait for the content to load
5. Go to another tab in Chrome and wait 30+ seconds.
6. Return to the AdSense setup tab and see an error

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

• The AdSense setup should not trigger an error (baseName is required) when it resets the error after the refocus code is triggered when the user navigates away from and back to the tab with AdSense setup open.

Implementation Brief

• [x] Remove the clearError() call from SetupMain in AdSense: https://github.com/google/site-kit-wp/blob/a84602fd1db5a2e89fe24943aae01ba29db6caf3/assets/js/modules/adsense/components/setup/SetupMain.js#L230
• [ ] Merge #8296

Test Coverage

• No test coverage needed.

QA Brief

• Follow steps to reproduce: you should not see an error.

Changelog entry

• Fix bug that could cause AdSense setup to display an error during setup when refocusing the tab after a period of inactivity.

[aaemnnosttv]

IB + CR ✅

For the QAB, this may be problematic if we can't consistently trigger the refocus callback as we saw re: #8297.

[mohitwp]

@tofumatt , In the QAB, this point states, "ensure your AdSense account status is set and not set to 'Ready'." However, it's not clear which AdSense account status should be set. Could you please clarify and update this point?

[tofumatt]

Ah, really any status other than the default, but these are the settings I used during testing:

[wpdarren]

QA Update: ✅

Verified:

• I recreated the error by following the steps to recreate it on the latest release.
• I switched to develop and completed the same steps, and no error message appeared in the console.

Screenshots