Don't show rate limits if the reset time has passed.

[iamdharmesh]

Description of the Change

In #354, we added an API rate limits widget to display the remaining API rate limits for the user and app. This PR makes a minor improvement by not showing the rate limits if the reset time has passed until the latest data is available.

How to test the Change

1. Tweet using one of the connected accounts and ensure that the rate limit starts appearing in the Dashboard widget and on the post edit screen.
2. Edit the autoshare_for_twitter_accounts option to set the reset time to a past value for one of the user accounts.
3. Verify that the rate limit no longer appears for that account and that it displays the message: "No X/Twitter rate limit available yet. Make a post to X/Twitter first." until new limit data becomes available.

Changelog Entry

Fixed - Ensure that no rate limits are shown if the reset time has passed.

Credits

Props @iamdharmesh

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[dkotter]

Code changes look good here.

While not related, both E2E tests and PHPUnit tests are failing because SVN is no longer installed by default in GitHub Actions.

The E2E tests should be fixed once 10up/action-wordpress-plugin-build-zip#8 is merged and a new release is put out.

For PHPUnit tests, we'll need to fix that on our end. Doesn't have to be done as part of this PR (could be a separate PR if you want) but would be great to resolve those. Can see how we fixed this on ClassifAI for an example

[dkotter]

Code changes look good here.

While not related, both E2E tests and PHPUnit tests are failing because SVN is no longer installed by default in GitHub Actions.

The E2E tests should be fixed once 10up/action-wordpress-plugin-build-zip#8 is merged and a new release is put out.

For PHPUnit tests, we'll need to fix that on our end. Doesn't have to be done as part of this PR (could be a separate PR if you want) but would be great to resolve those. Can see how we fixed this on ClassifAI for an example

E2E tests are fixed now with the upstream release. I've also fixed the PHPUnit tests in #358, so should be good on both once that is merged in