fixes #26874. Finished renaming display_settings to preferences. I had to change the name of some files to preferences in order to avoid conflicts.

[Shgit29]

Renamed Display settings to Preferences

Fixes: #26874

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

• [yes] Each commit is a coherent idea.
• [yes] 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.

[Shgit29]

All the checks have passed.

[Mahhheshh]

@Shgit29, Zulip follows its own commit guidelines. You can read about the commit disciplines and clean up your commit message history.

[Shgit29]

@Shgit29, Zulip follows its own commit guidelines. You can read about the commit disciplines and clean up your commit message history.

I will make sure to follow them the next time. This was my first time submitting a PR to zulip. Is it a must to fix it right now?

[Mahhheshh]

Is it a must to fix it right now?

Yes, you can squash your commits in a single one, and force push to current branch, it will fix the commit history. If you are new to github or parts that I have mentioned take a look git guide.

[Mahhheshh]

the commit message should be setting: Rename display settings to preferences..

[Shgit29]

the commit message should be setting: Rename display settings to preferences..

Hey, so I have changed the commit history now. Thank you so much for pointing it out, and providing me with a solution.

[Mahhheshh]

Thanks, could you please clear the commit description also??.

[Shgit29]

Thanks, could you please clear the commit description also??.

Done.

[Shgit29]

Thanks, could you please clear the commit description also??.

With the changes made, this PR is ready for review.

[alya]

Thanks for the fix! Could you please update your commit message to match the commit style guidelines?

[Shgit29]

Thanks for the fix! Could you please update your commit message to match the commit style guidelines?

Done.

[zulipbot]

Heads up @Shgit29, we just merged some commits that conflict with the changes you made in this pull request! You can review this repository's recent commits to see where the conflicts occur. Please rebase your feature branch against the upstream/main branch and resolve your pull request's merge conflicts accordingly.

[karlstolley]

You have just done a search-and-replace here. I'm closing this PR, because you're making changes to the logic and haven't carefully studied the impact of these changes. Once you understand the impact of your work, you're welcome to open another PR.