fix: Adjust padding in table cell and header components

[AIlkiv]

📝 Summary

I replaced the use of line-height with padding so that the text would be displayed correctly when it is in several lines.

The problem appeared after: #6150

🖼️ Screenshots

🏚️ Before	🏡 After

🚧 TODO

• ...

🏁 Checklist

• Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
• Sign-off message is added to all commits
• Tests (unit, integration and/or end-to-end) passing and the changes are covered with tests
• Documentation (README or documentation) has been updated or is not required

[mejo-]

Thanks for the contribution @AIlkiv, much appreciated! Could you fix the code style issues reported by prettier?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 52.53%. Comparing base (5024275) to head (93c7d12).
Report is 133 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7185      +/-   ##
==========================================
+ Coverage   51.85%   52.53%   +0.68%     
==========================================
  Files         479      479              
  Lines       41467    41522      +55     
  Branches     1004     1023      +19     
==========================================
+ Hits        21504    21815     +311     
+ Misses      19858    19605     -253     
+ Partials      105      102       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[AIlkiv]

@mejo- please, run pipeline again

[mejo-]

Tested and indeed fixes line padding. Thanks so much!

[mejo-]

/backport to stable31

[mejo-]

/backport to stable30

[mejo-]

/backport to stable31

[backportbot]

The backport to stable31 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable31
git pull origin stable31

# Create the new backport branch
git checkout -b backport/7185/stable31

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 93c7d12e

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/7185/stable31

Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/7185/stable31."} - https://docs.github.com/rest/pulls/pulls#create-a-pull-request

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)