fix!: make Image an HtmlComponent

[mstahv]

Currently our API exposes things like setText and add(Component), which can cause weird things and conflict with actual methods people would like to add to their extended components.

https://developer.mozilla.org/en-US/docs/Glossary/Void_element

Type of change

• Bugfix
• Feature

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Test Results

 1 397 files  ±0   1 397 suites  ±0   1h 15m 30s ⏱️ +29s
10 091 tests ±0  10 021 ✅ ±0  70 💤 ±0  0 ❌ ±0 
10 566 runs  ±0  10 487 ✅ ±0  79 💤 ±0  0 ❌ ±0 

Results for commit 87f79c3. ± Comparison against base commit 724cc06.

[mcollovati]

Great catch! However, this is a breaking change, so probably needs to be deferred to Vaadin 26.

[mstahv]

I would love to claim that highlighting broken code with a compilation error is not a backwards incompatible change, but maybe I'm just too liberal😎I wonder if somebody has abused the "feature" in some hack 🤔

[mcollovati]

@mstahv you were not so "liberal" when a not-so-different change broke a user add-on 😄

[mstahv]

I'm liberal to try and liberal to roll back if we find out some actual usage (that is not "just broken"). And we now have at least some add-on data via ecosystem build so I'm becoming more liberal all the time 😁