DOC: Move ecosystem.rst to getting started section (pandas-dev#52944)

* DOC: Move ecosystem.rst to getting started section

* Also error on ipython warnings

* Migrate existing ecosystem to web and fix references

Author: mroeschke

doc/data/tips.csv

@@ -321,7 +321,7 @@ def main():
         help=(
             "filename (relative to the 'source' folder) of section or method name to "
             "compile, e.g. 'development/contributing.rst', "
-            "'ecosystem.rst', 'pandas.DataFrame.join'"
+            "'pandas.DataFrame.join'"
         ),
     )
     argparser.add_argument(

doc/make.py

@@ -467,7 +467,6 @@
 }
 
 
-ipython_warning_is_error = False
 ipython_execlines = [
     "import numpy as np",
     "import pandas as pd",

doc/source/conf.py

@@ -60,7 +60,7 @@ Now users can access your methods using the ``geo`` namespace:
 
 This can be a convenient way to extend pandas objects without subclassing them.
 If you write a custom accessor, make a pull request adding it to our
-:ref:`ecosystem` page.
+`ecosystem <https://pandas.pydata.org/community/ecosystem.html>`_ page.
 
 We highly recommend validating the data in your accessor's ``__init__``.
 In our ``GeoAccessor``, we validate that the data contains the expected columns,
@@ -91,7 +91,7 @@ objects). Many methods like :func:`pandas.isna` will dispatch to the extension
 type's implementation.
 
 If you're building a library that implements the interface, please publicize it
-on :ref:`ecosystem.extensions`.
+on `the ecosystem page <https://pandas.pydata.org/community/ecosystem.html>`_.
 
 The interface consists of two classes.