Fixed #21018 -- Reversed precedence order for management commands.

        # a settings module.

        django.setup()

        app_configs = apps.get_app_configs()

        app_names = [app_config.name for app_config in app_configs]

        app_names = [app_config.name for app_config in reversed(app_configs)]

    # Find and load the management module for each installed app.

    for app_name in app_names:

    These rules apply regardless of whether :setting:`INSTALLED_APPS`

    references application configuration classes on application packages.

When several applications provide different versions of the same resource

(template, static file, management command, translation), the application

listed first in :setting:`INSTALLED_APPS` has precedence.

.. setting:: INTERNAL_IPS

INTERNAL_IPS

* The ``only_installed`` argument of ``get_model`` and ``get_models`` no

  longer exists, nor does the ``seed_cache`` argument of ``get_model``.

Management commands and order of :setting:`INSTALLED_APPS`

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

When several applications provide management commands with the same name,

Django loads the command from the application that comes first in

:setting:`INSTALLED_APPS`. Previous versions loaded the command from the

applicatino that came last.

This brings discovery of management commands in line with other parts of

Django that rely on the order of :setting:`INSTALLED_APPS`, such as static

files, templates, and translations.

Behavior of ``LocMemCache`` regarding pickle errors

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~