[stable28] fix(theming): Apply same logic on capabilities for primary color as done on themes

[susnux]

• Backport of fix(theming): Apply same logic on capabilities for primary color as done on themes #43033

Summary

On themes we replace the default color with the accessible color, so we also need to do this on the capabilities.
This worked previously but as we now enforce contrasts of the text color clients that use the capabilities changes to black text on that color.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[SystemKeeper]

For my understanding, why not adjust this in

server/apps/theming/lib/ThemingDefaults.php

Lines 508 to 510 in 64ccc1e

	publicfunctiongetTextColorPrimary() {
	return$this->util->invertTextColor($this->getColorPrimary()) ? '#000000' : '#ffffff';
	}

🤔

[susnux]

For my understanding, why not adjust this in

Better would be in getColorPrimary, but that would have greater consequences especially for a stable branch I would not change that API and just fix the usage here.

For a general fix I currently prepare this one: #42977

[susnux]

cypress unrelated