Move away from icon as VueComponents

[skjnldsv]

Using button icons as VueComponent can lead to issues.
If the components are compiled with different vue versions, this will collide and fail. We had that issue multiple times on variuos other APIs.

Which is why we moved to raw svg as this is the only standard that works whatever js pre-processor or vanilla js code you're handling.

[susnux]

This should be no problem, passing components is fine as long as the vue version (2 vs 3) is not mixed.
Otherwise we would not be able to use nextcloud-vue components in other apps / projects as this is the same: you pass a compiled component to a different vue.

[skjnldsv]

Nope, we had that issue in the past.
Even in 2.x, the template compiler generated different outputs and created some incompatibilities

[susnux]

but even if the result of the template compiler is different it should work as only the render function will be different.
of cause you can not use any breaking changes of the vue API. Especially as this is something vue promotes.

[skjnldsv]

🤷We had to downgrade a few vue versions in the past to keep being able to release between apps and libs.
That happened with Server and other Libraries.
Since we're now mostly stuck at 2.7.x, it "fixed" itself. But the underlying issue still happened 🤷

Also, same with vue3, it means we're implementing a breaking point.
While if we'd be using svg, it would not matter, it would work out of the box, even if this library was vue3 and the app vue2.