chore: don't prevent users from entering the env form when they're at…

… the limit (#7549)

This change reverts the changes related to the button in particular
that were introduced in #7500. The button is now always enabled, and
the actual resource warning and creation blocking happens in the form,
courtesy of #7548.

frontend/src/component/environments/CreateEnvironmentButton/CreateEnvironmentButton.tsx

@@ -3,29 +3,18 @@ import Add from '@mui/icons-material/Add';
 import { ADMIN } from 'component/providers/AccessProvider/permissions';
 import useUiConfig from 'hooks/api/getters/useUiConfig/useUiConfig';
 import { useNavigate } from 'react-router-dom';
-import { useEnvironments } from 'hooks/api/getters/useEnvironments/useEnvironments';
 
 export const CreateEnvironmentButton = () => {
     const { uiConfig } = useUiConfig();
-    const { environments } = useEnvironments();
-    const environmentLimit = uiConfig.resourceLimits.environments;
     const navigate = useNavigate();
 
-    const limitReached = environments.length >= environmentLimit;
-
     return (
         <ResponsiveButton
-            tooltipProps={{
-                arrow: true,
-                title: limitReached
-                    ? `You have reached the limit of environments you can create (${environmentLimit}).`
-                    : undefined,
-            }}
             onClick={() => navigate('/environments/create')}
             maxWidth='700px'
             Icon={Add}
             permission={ADMIN}
-            disabled={limitReached || !uiConfig.flags.EEA}
+            disabled={!uiConfig.flags.EEA}
         >
             New environment
         </ResponsiveButton>