These tests won't be ran when imported from the corporate site.

All the translation tests manage different user permissions on each
different project, which is more complicated to test them from
Corporate. So, they are marked as `only_community`

When loading this test from outside (readthedocsinc) the ``reverse``
can't be calculated because the ``search`` name is not defined in the URLConf.

Accessing ``/`` while logged in redirects to ``/dashboard/`` in the
corporate site. This change makes this test compatible with both environments

Since this is executed even when the test is skipped, we need to use
the ``_lazy`` function.

This Feature is created inside a db migration. As we depend strictly
on this Feature we can't rely on data from the migration since it's
ran only once when the db is created and not re-populated on each
test.

We need to be sure that the data we rely on is in the database in a
valid state and that it wasn't modified/deleted by any other test
case. Because of this, we need to use a fixture or delete and create
the data we rely on inside the ``setUp`` for this test.

These tests performs a call to our API from a signal hook in our
corporate site and the API call in that file is not mocked, so they fail.

These tests are excluded from the corporate site using pytest internals.