Replace dependency @material-ui/core with @mui/material

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
@material-ui/core (source) → @mui/material	dependencies	replacement	^4.2.1 → ^5.0.0

⚠️ Renovate's replacement functionality does not currently wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).

This is a special PR that replaces @material-ui/core with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: (in timezone US/Eastern)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

/opt/containerbase/tools/corepack/0.34.6/14.18.2/node_modules/corepack/dist/yarn.js:2
process.env.COREPACK_ENABLE_DOWNLOAD_PROMPT??='1'
                                           ^^^

SyntaxError: Unexpected token '??='
    at wrapSafe (internal/modules/cjs/loader.js:1001:16)
    at Module._compile (internal/modules/cjs/loader.js:1049:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
    at Module.load (internal/modules/cjs/loader.js:950:32)
    at Function.Module._load (internal/modules/cjs/loader.js:790:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47

[sentry]

Bug: The dependency update to MUI v5 is incomplete. All import paths and API calls in the code still reference the old v4 package and function names, which will break the build.
_{Severity: CRITICAL}

Suggested Fix

Update all import statements from @material-ui/core to the new @mui/material package. Run a codemod or manually refactor the code to use the new v5 APIs, such as renaming createMuiTheme to createTheme and MuiThemeProvider to ThemeProvider.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The pull request updates Material-UI from version 4 to version 5 in
`package.json` but fails to update the corresponding code. The entire codebase still
contains over 100 import statements from the old package name, `@material-ui/core`,
which has been removed. Additionally, the code uses v4 APIs like `createMuiTheme` and
`MuiThemeProvider`, which were renamed to `createTheme` and `ThemeProvider` in v5. These
issues will cause the application build to fail with module resolution errors,
preventing deployment.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The dependency @material-ui/core was upgraded to @mui/material v5, but the codebase was not migrated, causing fatal import errors and breaking API changes.
_{Severity: CRITICAL}

Suggested Fix

Follow the official Material-UI v4 to v5 migration guide. Run the automated codemods to update package names, imports, and common API changes (e.g., createMuiTheme to createTheme). Manually review and fix any remaining breaking changes, such as component prop updates (e.g., Checkbox onCheck to onChange).

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The `package.json` is updated from `@material-ui/core` v4 to
`@mui/material` v5, but the application code has not been updated to reflect this major
version upgrade. The codebase contains over 140 files that still import from the old
`@material-ui/core` package. Since this old package will no longer be installed, the
application will fail to start due to module import errors. Additionally, even if the
imports were fixed, the code uses APIs like `createMuiTheme`, `MuiThemeProvider`, and
component props like `onCheck` and `inputStyle` that were renamed or removed in v5,
which would cause runtime failures.

[sentry]

Bug: The upgrade to @mui/material v5 is incomplete, as it requires React v17+ and the peer dependencies @emotion/react and @emotion/styled, which are missing.
_{Severity: CRITICAL}

Suggested Fix

Update the react and react-dom dependencies to version 17.0.0 or higher. Additionally, add the required peer dependencies for MUI v5 by running npm install @emotion/react @emotion/styled.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The project's `package.json` is being updated to use `@mui/material`
v5, but this upgrade is incomplete, introducing multiple issues. Firstly, MUI v5
requires `react` version 17.0.0 or higher, but the project is configured to use `react`
version ~16.8. Secondly, MUI v5 has required peer dependencies, `@emotion/react` and
`@emotion/styled`, which have not been added to the `package.json`. While there is a
more immediate build-breaking issue due to outdated import paths in the code, these
dependency incompatibilities will cause application failures once the import paths are
corrected.

[sentry]

Bug: The application will fail to start because it still imports from @material-ui/core, which is being removed as a dependency in favor of @mui/material.
_{Severity: CRITICAL}

Suggested Fix

Update all import statements throughout the codebase to use the new MUI v5 package names. For example, change imports from @material-ui/core to @mui/material. Also, update API calls that were renamed, such as createMuiTheme to createTheme and MuiThemeProvider to ThemeProvider.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The `package.json` is updated to replace `@material-ui/core` with
`@mui/material`, but the codebase still contains numerous import statements referencing
the old package, such as `import { MuiThemeProvider, createMuiTheme } from
"@material-ui/core/styles"`. Since the `@material-ui/core` package will no longer be
installed, these imports will fail during module resolution. This will cause the
application to crash on startup or fail during the build process, preventing it from
running.

[sentry]

Bug: The Checkbox component is passed an onCheck prop, which was removed in MUI v5. This will cause checkboxes to be unresponsive to user clicks.
_{Severity: HIGH}

Suggested Fix

Update all instances of the Checkbox component to use the onChange prop instead of onCheck. Additionally, review the entire codebase for other MUI v4 to v5 breaking changes, such as renaming createMuiTheme to createTheme and updating all import paths from @material-ui/core to @mui/material.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L11

Potential issue: The application's dependency was updated from Material-UI v4 to MUI v5,
but the code was not updated to reflect the breaking API changes. Specifically,
components like `Checkbox` are still being passed the `onCheck` prop, which was replaced
by `onChange` in v5. While the application will fail to load due to incorrect import
paths (e.g., using `@material-ui/core` instead of `@mui/material`), if those paths were
corrected, this underlying API mismatch would cause a functional bug. Checkboxes would
not respond to user clicks because the event handler is attached to an unrecognized
prop, breaking functionality in areas like profile forms.