fix: adjusted highlight color for multi select elements

[kwhuber]

Fixes #7262

This PR introduces changes to fix a styling issue with the Select component in Form.tsx.

Specifically, the class added to selected options was too light when using 'dark:bg-neutral-100', hence the following change:

specify7/specifyweb/frontend/js_src/lib/components/Atoms/Form.tsx

Lines 350 to 359 in e89852b

	/*
	* Selected options in an optional multiple select are clashing with
	* the background in dark-mode. This is a fix:
	*/
	if (props.required !== true && props.multiple === true) {
	selected.map((option) => option.classList.add('dark:bg-neutral-500')); // highlights selected object less bright
	unselected.map((option) =>
	option.classList.remove('dark:bg-neutral-500') // prevents a previously selected option from remaining highlighted
	);
	}

After following the testing instructions, this was the result prior to the fix:

Following the fix and after selecting the chronostrat then clicking outside of the pick list, this is the corrected behavior:

Screen.Recording.2025-10-27.at.1.32.58.PM.mov

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

This must be tested in a Geology, Vertebrate Paleontology, or Invertebrate Paleontology discipline. I used the uw_geo_collections_2025_09_09.sql database and then the Fossil Vertebrates collection.

• Create a Collection Object query, add the Age field to the mapping, add the Name operator, select an item from the list
• Click away from the list and see that the item turns a very light grey color
• Verify another query with a select option in a different database (and add that example to your review)

[grantfitzsimmons]

@kwhuber Nice work! I suggest retitling this issue to reflect the underlying change instead of focusing on just one result. Sometimes, users or testers create issues with very narrow titles (e.g., "Dark Mode: Selected chronostrat in dropdown for age 'Name' queries is too bright to read"), but the actual change affects all multi-select elements in the app.

[emenslin]

• Create a Collection Object query, add the Age field to the mapping, add the Name operator, select an item from the list
• Click away from the list and see that the item turns a very light grey color
• Verify another query with a select option in a different database (and add that example to your review)

Looks good, I tested on ojsmnh with the storage information picklist using the 'in' operator.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[Iwantexpresso]

• Create a Collection Object query, add the Age field to the mapping, add the Name operator, select an item from the list

• Click away from the list and see that the item turns a very light grey color
  Verify another query with a select option in a different database (and add that example to your review)

• Verify another query with a select option in a different database (and add that example to your review)

it looks great! I tested on Geo_swiss database using "in" and the Collection Object type pick-list

[CarolineDenis]

@kwhuber could you remove all the files that are not necessary for this pr?

[acwhite211]

Add a commit to reverse the newline changes in the docker-compose.yml, Dockerfile, and manage.py files. 👍