Revert "refactor: move common/lib/capa/capa to xmodule/capa" (#30762)

docs/guides/conf.py

@@ -20,6 +20,7 @@ root = Path('../..').abspath()
 # can be successfully imported
 sys.path.insert(0, root)
 sys.path.append(root / "docs/guides")
+sys.path.append(root / "common/lib/capa")
 
 
 # Use a settings module that allows all LMS and Studio code to be imported
@@ -220,6 +221,7 @@ autodoc_mock_imports = [
 # the generated *.rst files
 modules = {
     'cms': 'cms',
+    'common/lib/capa/capa': 'common/lib/capa',
     'lms': 'lms',
     'openedx': 'openedx',
     'xmodule': 'xmodule',

docs/guides/docstrings/common_lib.rst

@@ -7,3 +7,5 @@ out from edx-platform into separate packages at some point.
 
 .. toctree::
     :maxdepth: 2
+
+    common/lib/capa/modules

docs/guides/testing/testing.rst

@@ -71,7 +71,7 @@ Test Locations
 
 -  Python unit and integration tests: Located in subpackages called
    ``tests``. For example, the tests for the ``capa`` package are
-   located in ``xmodule/capa/tests``.
+   located in ``common/lib/capa/capa/tests``.
 
 -  Javascript unit tests: Located in ``spec`` folders. For example,
    ``xmodule/js/spec`` and
@@ -432,7 +432,7 @@ Factories are often implemented using `FactoryBoy`_.
 
 In general, factories should be located close to the code they use. For
 example, the factory for creating problem XML definitions is located in
-``xmodule/capa/tests/response_xml_factory.py`` because the
+``common/lib/capa/capa/tests/response_xml_factory.py`` because the
 ``capa`` package handles problem XML.
 
 .. _FactoryBoy: https://readthedocs.org/projects/factoryboy/