title: Changed import structure in Django 3.2?
body: <p>I just opened a new Djangoproject with v3.2 and tried to import my apps as usual, when I got an ImproperlyConfigured Exception on one of my apps.</p>
  <p>Steps:</p>
  <ol>
  <li>create and activate env, pip install django (without version number defaults to v3.2 as of now)</li>
  <li>django-admin startproject project</li>
  <li>mkdir project\apps, mkdir project\apps\core</li>
  <li>django-admin startapp core project\apps\core</li>
  <li>migrate, if necessary</li>
  <li>Go to settings and add 'apps.core' to INSTALLED_APPS</li>
  </ol>
  <p>The result, when trying to runserver</p>
  <pre><code>\lib\site-packages\django\apps\config.py&quot;, line 246, in create
  raise ImproperlyConfigured(
  django.core.exceptions.ImproperlyConfigured: Cannot import 'core'. Check that 
  'apps.core.apps.CoreConfig.name' is correct.
  </code></pre>
  <p>Structure</p>
  <pre><code>-- project
    -- apps
      -- core
        -- apps.py
    -- project
    -- manage.py
  </code></pre>
  <p>core\apps.py</p>
  <pre><code>class CoreConfig(AppConfig):
  default_auto_field = 'django.db.models.BigAutoField'
  name = 'core'
  </code></pre>
  <p>The auto_field seems to be new as it was not integrated in earlier versions, however, this should not affect the importation if I understand this correctly.</p>
  <p>I returned to v3.1.3 to check if something else went wrong, but it is working fine with this approach.</p>
  <p>Does anyone have the same issues or have a solution?</p>
  <p>Thanks</p>