Fix: Correcting the break in large topics on the card (temp).

[lucaslobatob]

Description

Adjusting large topics with maxWidth to prevent card breakage temp.

Related Ticket # (issue)

Type of change

Please delete options that are not relevant.

• [X] 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

Steps:

1. Log in to the platform.
2. Create a sentence or open an existing one.
3. Add a topic with many characters, such as "Conferência das Nações Unidas sobre as Mudanças Climáticas em 2025".
4. Go to the Home page and view the card for the sentence where you added the large topic.

Before

After

Developer Checklist

General

• [X] No console.log or related logging is added.
• [X] 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).

Frontend Changes

• [X] No new styling is added through CSS files (Unless it's a bugfix/hotfix)
• [X] 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

Test IDs

• [ ] Include the test ID when adding new tasks or components.
• [ ] Check that test IDs are present in the modified components.

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 Project do Github 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.

[sonarqubecloud[bot]]

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

[Keikonichi]

@lucaslobatob @snowmous3

Wouldn't it be more interesting to break up the text so that the entire COP30 title is visible, since it is a prominent topic?