fix: Deletion allowed in FluentSearch that is ReadOnly or Disabled

[ASchweers]

🐛 Bug Report

In a <FluentSearch>-component, where the Disabled or ReadOnly parameter is set to true, the 'X'-button on the right hand side disappears. But the button is only hidden and still clickable, resulting in deletion of the value.

💻 Repro or Code Sample

See the Search-page of the demo and try the States-sample:

• type something in one of the first three <FluentSearch>-components
• now you can delete the value, if you click on the far right edge of the readonly or disabled <FluentSearch>-component.

🤔 Expected Behavior

Deletion shouldn't be possible in this scenario.

[PascalVorwerk]

I have this fixed locally by adding a disabled attribute to the button if the Disabled or Readonly property on the components are either true. Setting a readonly attribute on the button didn't fix it for the readonly attribute.. cause a readonly button still handles clicks.

Let me know if you want me to open a PR for this!

20250222-2336-19.5674772.mp4

I still need to add some tests aswell, but waiting to hear first. I do think some unit tests will start failing now because we are adding attributes to the HTML generated..

[vnbaaij]

Yes, please create a PR for this. We can fix the unit tests. There are other components where we are adding attributes as well.