[JENKINS-71115] Builds filter field doesn't use full width on sub 970px windows

[niralmaruda]

Removed max-width:420 from search-bar.scss which resolved the issue

• After changes the Build filter field is flexible with relative to browser window size.
• This pull request does not have any test because the changes was in scss file.
• Kindly do let me know if I have missed anything by chance.

See JENKINS-71115.

Testing done

• I have build and tested on my PC and it works as needed.
• The Build filter filed cover size with respect to browser window.

Proposed changelog entries

• Show full width filter field for builds on pages less than 970 pixels wide.

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).
  • Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.

Desired reviewers

New to this community. Happy to connect with anyone to build long term friendship/mentorship.

Maintainer checklist

Before the changes are marked as ready-for-merge:

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[daniel-beck]

While this looks like a simple fix, I wonder whether this breaks something else. Originally added in #7074 #5842 so @janfaracik should be able to explain the purpose of the rule.

[janfaracik]

If I remember correctly the max width was for the New node page -

Before

After

I'm good either way with the size. Setting a more specific selector would have been a better move on my part in #5842.

[NotMyFault]

Thanks!

---

/label ready-for-merge

---

This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!