1505 - Migrate Button component from Ant Design to MUI

[lucaslobatob]

Description

*Button.tsx: Migrate Button component from Ant Design to Material-UI

• Replaced Ant Design's Button with Material-UI's Button in the project.
• Updated all references to AntD's ButtonProps and related APIs.
• Introduced buttonType to map custom button styles previously managed with AntD's type.
• Replaced htmlType with type for handling button functionality (submit, reset, button).
• Updated usage of loading, icon, and other AntD-specific props to Material-UI equivalents.
• Ensured compatibility with href, target, and style props in the new implementation.*

Fixes #1505

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Existing feature enhancement (non-breaking change which modifies existing functionality)

Testing

1. Be logged into the platform;
2. Click on any button within the platform; and
3. See if you are redirected to the correct page that the button corresponds to.

Developer Checklist

General

• Code is appropriately commented, particularly in hard-to-understand areas
• Repository documentation has been updated (Readme.md) with additional steps required for a local environment setup.
• No console.log or related logging is added.
• No code is repeated/duplicated in violation of DRY. The exception to this is for new (MVP/Prototype) functionality where the abstraction layer may not be clear (comments should be added to explain the violation of DRY in these scenarios).
• Documented with TSDoc all library and controller new functions

Frontend Changes

• No new styling is added through CSS files (Unless it's a bugfix/hotfix)
• All types are added correctly

Tests

• All existing unit and end to end tests pass across all services
• Unit and end to end tests have been added to ensure backend APIs behave as expected

Merge Request Review Checklist

• An issue is linked to this PR and these changes meet the requirements outlined in the linked issue(s)
• High risk and core workflows have been tested and verified in a local environment.
• Enhancements or opportunities to improve performance, stability, security or code readability have been noted and documented in JIRA issues if not being addressed.
• Any dependent changes have been merged and published in downstream modules
• Changes to multiple services can be deployed in parallel and independently. If not, changes should be broken out into separate merge requests and deployed in order.

[thesocialdev]

@lucaslobatob these changes are failing in cypress and you should take a look.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud