Handle failed API requests on schema page

[nikhilhenry]

Fixes #2644

Adds UI elements to display API request errors when fetching tables and queries (explorations) on the schema page in accordance with the provided design reference.

Technical details

• Refactor table store to use RequestStatus instead of previously deprecated State.
• Add support to manually refetch tables and queries.
• Add support to redirect to the database page.
• Display errors using the ErrorBox component.

Screenshots

Note: This PR is heavily inspired by PR #2829. Thanks to authors for their work!

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the develop branch of the repository
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[pavish]

@nikhilhenry Thanks for the PR! I have a few comments which need to be addressed before merging this in.

Additionally, I notice that this PR does not satisfy the linting rules. Please fix them before marking it as ready for review again.

[pavish]

@nikhilhenry I'm still seeing some linting errors, and a number of test changes that seem to have made into this PR. Please fix them and double check before requesting review.

[nikhilhenry]

@pavish I've reverted the changes to the backend and changes to stores/tables.ts and stores/queries.ts using git revert.

Could you please let me know if this is the appropriate method to revert these changes or if it would be better for me to open a new PR?

Once again, really sorry for the confusion.

[pavish]

@nikhilhenry Looks good to me! Thanks for your work on this.