BREAKING(fs,dotenv): drop Deno v1.x support

[iuioiua]

This PR drops Deno v1.x from being used in CI, or rather it just removes the guarantee that the Standard Library will work with Deno v1.x (even though it does 99% of the time). I think this is reasonable to do now as Deno 2 is LTS.

The title is accurate but may seem more significant than these changes are. This just changes the expected error when insufficient permissions are granted for some operations in @std/fs and @std/dotenv. See Deno.errors.NotCapable.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.93%. Comparing base (6a00d6c) to head (7323cfd).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6624      +/-   ##
==========================================
- Coverage   94.75%   93.93%   -0.82%     
==========================================
  Files         584      579       -5     
  Lines       46563    41461    -5102     
  Branches     6541     6512      -29     
==========================================
- Hits        44119    38948    -5171     
- Misses       2401     2464      +63     
- Partials       43       49       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kt3k]

v1 is still significantly used according to our internal check. (Probably many users are still stuck with v1 because of CLI's breaking changes)

I don't think we are ready to do this change.

cc @bartlomieju @ry

[kt3k]

If we drop v1 CI, we don't what packages work in v1 anymore (any package could randomly break in v1 in the future development)