Clarify known issue for mgmt console after upgrade (github#28612)

Author: solvaholic

data/release-notes/enterprise-server/3-5/0.yml

@@ -342,6 +342,15 @@ sections:
       It is now possible for GitHub Apps to upload release assets.
 
   changes:
+  
+      # https://github.com/github/docs-content/issues/7435
+    - |
+        Minimum requirements for root storage and memory increased for GitHub Enterprise Server 2.10 and 3.0, and are now enforced as of 3.5.0.
+
+          - In version 2.10, the minimum requirement for root storage increased from 80 GB to 200 GB. As of 3.5.0, system preflight checks will fail if the root storage is smaller than 80 GB.
+          - In version 3.0, the minimum requirement for memory increased to from 16 GB to 32 GB. As of 3.5.0, system preflight checks will fail if the system has less than 28 GB of memory.
+
+        For more information, see the minimum requirements for each supported deployment platform in "[Setting up a GitHub Enterprise Server instance](/enterprise-server/admin/installation/setting-up-a-github-enterprise-server-instance)." [Updated: 2022-06-20]
     # https://github.com/github/releases/issues/2063
     - |
       To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)."
@@ -417,4 +426,4 @@ sections:
       - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
       - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
       - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. [Updated: 2022-06-08]'
-      - 'The Management Console cannot be accessed on an under-provisioned instance. [Updated: 2022-06-14]'
+      - 'Management Console may appear stuck on the _Starting_ screen after upgrading an under-provisioned instance to GitHub Enterprise Server 3.5. [Updated: 2022-06-20]'

data/release-notes/enterprise-server/3-5/1.yml

@@ -29,3 +29,4 @@ sections:
       - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
       - Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
       - 'Deleted repositories will not be purged from disk automatically after the 90-day retention period ends. This issue is resolved in the 3.5.1 release. [Updated: 2022-06-10]'
+      - 'Management Console may appear stuck on the _Starting_ screen after upgrading an under-provisioned instance to GitHub Enterprise Server 3.5. [Updated: 2022-06-20]'