chore: remove all reference for bok-choy

.dockerignore

@@ -89,7 +89,6 @@ test_root/paver_logs/
 test_root/uploads/
 **/django-pyfs
 **/.tox/
-common/test/db_cache/bok_choy_*.yaml
 common/test/data/badges/*.png
 
 ### Installation artifacts

cms/envs/test_static_optimized.py

@@ -1,10 +1,6 @@
 """
 Settings used when generating static assets for use in tests.
 
-For example, Bok Choy uses two different settings files:
-1. test_static_optimized is used when invoking collectstatic
-2. bok_choy is used when running CMS and LMS
-
 Note: it isn't possible to have a single settings file, because Django doesn't
 support both generating static assets to a directory and also serving static
 from the same directory.

lms/envs/test_static_optimized.py

@@ -1,10 +1,6 @@
 """
 Settings used when generating static assets for use in tests.
 
-For example, Bok Choy uses two different settings files:
-1. test_static_optimized is used when invoking collectstatic
-2. bok_choy is used when running CMS and LMS
-
 Note: it isn't possible to have a single settings file, because Django doesn't
 support both generating static assets to a directory and also serving static
 from the same directory.

openedx/tests/xblock_integration/xblock_testcase.py

@@ -71,7 +71,7 @@ class XBlockEventTestMixin:
     2. assert_event_published verifies that an event of a given search
         specification was published.
 
-    The Mongo/bok_choy event tests in cohorts have nice examplars for
+    The Mongo event tests in cohorts have nice examplars for
     how such functionality might look.
 
     In the future, we would like to expand both search

scripts/generic-ci-tests.sh

@@ -20,11 +20,10 @@ set -e
 #       - "pavelib-unit": Run Python unit tests from the pavelib/lib directory
 #       - "pavelib-js-unit": Run the JavaScript tests and the Python unit
 #           tests from the pavelib/lib directory
-#       - "bok-choy": Run acceptance tests that use the bok-choy framework
 #
 #   `SHARD` is a number indicating which subset of the tests to build.
 #
-#       For "bok-choy" and "lms-unit", the tests are put into shard groups
+#       For "lms-unit", the tests are put into shard groups
 #       using the 'attr' decorator (e.g. "@attr(shard=1)"). Anything with
 #       the 'shard=n' attribute will run in the nth shard. If there isn't a
 #       shard explicitly assigned, the test will run in the last shard.