FIX-#5252: Disable notebook tests until access control issues are resolved for modin-test bucket

[RehanSD]

Signed-off-by: Rehan Durrani rehan@ponder.io

What do these changes do?

• first commit message and PR title follow format outlined here

  NOTE: If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

• passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
• passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
• signed commit with git commit -s
• Resolves TEST: CI: CI broken because of 403 HTTPError for taxi CSV on modin-test s3 #5252
• tests added and passing
• module layout described at docs/development/architecture.rst is up-to-date

[RehanSD]

Should we add a fix for the places where the bucket is referred to in the docs?

[YarShev]

Should we add a fix for the places where the bucket is referred to in the docs?

Maybe some note should be added? Am I correct that other notebooks (e.g., quickstart.ipynb) also don't work for now as those refers to https://modin-test.s3.us-west-1.amazonaws.com/yellow_tripdata_2015-01.csv?

[RehanSD]

Should we add a fix for the places where the bucket is referred to in the docs?

Maybe some note should be added? Am I correct that other notebooks (e.g., quickstart.ipynb) also don't work for now as those refers to https://modin-test.s3.us-west-1.amazonaws.com/yellow_tripdata_2015-01.csv?

Yep - any notebook referencing those buckets will fail to run - happy to add a note if folks would like, but maybe we should merge this PR first since it's blocking CI on everything else?

[mvashishtha]

but maybe we should merge this PR first since it's blocking CI on everything else?

Yep, that's what I would like to do. I will file a follow-up issue for the long term fix, too.