fix: app card description truncation

[deepanshurajput0]

What does this PR do?

Resolves inconsistent truncation of app card descriptions on the /apps page. Long descriptions now properly truncate after 3 lines with ellipsis (...) and all card heights are consistent.

• Fixes [bug]: line-clamp property does not truncate long texts properly in app card description #23659

Image Demo (if applicable):

Original

Updated

Mandatory Tasks (DO NOT REMOVE)

I have self-reviewed the code.
I have updated the developer docs in /docs if applicable. N/A.
I confirm automated tests are in place or feature verified.

How should this be tested?

Navigate to /apps page locally.
Verify both short and long descriptions:
Long descriptions truncate after 3 lines.
Ellipsis (...) appears consistently.
Card heights remain uniform.
Minimal test data: at least one card with a description longer than 3 lines.
No environment variables are required.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ anikdhabal
❌ Deepanshu Verma

---

Deepanshu Verma seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Fix app card description truncation ". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[cubic-dev-ai]

No issues found across 1 file

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion