Various changes

[brl0]

These changes are broken out from the result of some long running tinkering I started a couple of years ago. To help keep the review process reasonable, I am trying to strike a balance of not creating too many small PRs while also not creating overly large PRs. Along those lines I am willing to break out or combine change sets in whatever manner is most comfortable for review, just let me know.

Changes in this PR:

• Improve some error messages by including the string value of the path so it is clear what failed.
• Refactored __new__, extracting a method for creating paths from other path objects to improve readability and clarity.
• Cleaned up notebook for clarity and brevity, also added table of fsspec supported filesystems.
• Added custom warning to make it easier to filter, also added simple function to do so.
• Fixed bug causing incorrect rglob results (top level glob matches were not included).
• GitHub Actions
  • Only run on PRs and pushes to main, to fix duplicate runs.
  • Don't fail fast, so that multiple failures can be reviewed after each run.
  • Run on "3.11" rather than "3.11-dev".

Changes split out for later:

• Refactor tests and fixtures for improved isolation.
  • Make it easier and safer to allow for tests to be run live.
  • Reduce inadvertent test interaction and flakiness.
  • Eventually try to use UPath's great test suite directly from other fsspec filesystem projects to improve coverage.
• Migrate to hatch, stop using legacy setup metadata format.
• Update and consolidate dev tools and test dependencies.
• New nox tasks and minor changes for convenience.
• Add, configure, and apply pre-commit for consistent code formatting.

I'd be eager for any feedback or suggestions. Thanks!

[ap--]

Thank you so much for your contribution!

I went through and made some comments.
Regarding the other changes you mentioned in the PR text, I would suggest to open a new issue, so we can discuss how to move forward.

Let me know what you think,
Andreas

[ap--]

Hi @brl0,

I opened two new issues for the remaining items you mentioned in the PR text.

Cheers,
Andreas 😃

[brl0]

Hey @ap--,

Thanks so much for your timely and thorough review, I enjoy learning from feedback and really appreciate your time.

I made some changes and responded to some of your comments and would love to hear any more of your thoughts.

[brl0]

@ap--,

I thought I'd follow up to see if my changes were acceptable, and to see if you had any more feedback on this PR.

[ap--]

Thank you for addressing the comments and adding the tests ❤️

There's one small change left, and then we're good to merge this.

[brl0]

@ap--,

Thanks again for your review. I have made the requested changes.
I'm curious about your thoughts on my comment in #90.

Once this gets merged, I'll put together a PR with the refactored tests.

[ap--]

Thank you @brl0 ❤️

This is a great improvement. I'll merge this now and will prepare a new release over the weekend.

Also thank you so much for your patience 🙇 It's been a few busy weeks over here...
When we move forward with the other improvements let's break them up into individual pieces when it makes sense to speed up the process as much as possible.