Fixes #26480 : Prevent color leak due to dragging of table row in settings and custom profile fields

[Kota-Karthik]

Fixes: #26480

Screenshots and screen captures:
These are screenshots and screen captures after i have made the changes:-

After_Changes_Final.mov

Self-review checklist

• Self-reviewed the changes for clarity and maintainability
  (variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

• Explains differences from previous plans (e.g., issue description).
• Highlights technical choices and bugs encountered.
• Calls out remaining decisions and concerns.
• Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

• Each commit is a coherent idea.
• Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

• Visual appearance of the changes.
• Responsiveness and internationalization.
• Strings and tooltips.
• End-to-end functionality of buttons, interactions and flows.
• Corner cases, error conditions, and easily imagined bugs.

I had adjusted the background color value which was causing the problem @timabbott Kindly review the PR and please tell me weather any changes needed!! Thank You : )

[Kota-Karthik]

@timabbott
I had made the PR for #26480
kindly review it and please tell me whether any changes needed!!

[amanagr]

This changes color for a a lot of elements, can we just keep it scoped to the tables we want to fix the background for. Also, looks like there is white border in you video when drag the table row, would be great to remove that too.

[Kota-Karthik]

ok ,I will do the required changes wherever needed and will inform you , once its done!!
Thank You : )

[Kota-Karthik]

@amanagr
color changes scoped to tables we want to fix the background color for
But i was not able to solve the problem of that white border while dragging the table row
I was not able to find the CSS for which this problem keeps occuring
But as per the issue #26480 I have solved it
It would be great , if you review this once again
Thank You : )

[amanagr]

Well, I cannot approve this PR until my comment is addressed.

[Kota-Karthik]

@amanagr
I would fix that white border issue
but could you tell me whether the other changes I made are correct and have no problem ?
Thank You: )

[amanagr]

This changes color for a lot of elements, can we just keep it scoped to the tables we want to fix the background for.

[Kota-Karthik]

@amanagr
color changes scoped to tables we want to fix the background color for
as per the issue #26480 I have solved it
It would be great , if you review this once again
Thank You : )

[Kota-Karthik]

@amanagr
It would be great if you can review this PR
and let me know if any changes needed
Thank You: )

[zulipbot]

Hello @Kota-Karthik, it seems like you have referenced #26480 in your pull request description, but you have not referenced them in your commit message description(s). Referencing an issue in a commit message automatically closes the corresponding issue when the commit is merged, which makes the issue tracker easier to manage.

Please run git commit --amend in your command line client to amend your commit message description with Fixes #26480..

An example of a correctly-formatted commit:

commit fabd5e450374c8dde65ec35f02140383940fe146
Author: zulipbot
Date:   Sat Mar 18 13:42:40 2017 -0700

    pull requests: Check PR commits reference when issue is referenced.

    Fixes #51.

To learn how to write a great commit message, please refer to our guide.