Its not off topic at all, the issue here is that Joomshaper seen to produce templates and components that they do not support for future versions and templates.
I partly understand your disappointment, if something does not work as expected...
But I don't see a real problem, where Joomshaper is to blame for?!
The Glamour template has been updated, the HELIX2 framework seem to work in latest Joomla, and the PageBuilder v2 seem to work as well. Or what do you mean by "future versions"?
That other topic was mine also and the answer is not good enough.
I have read your topic. Actually, you were asking for a customization: Moving an Addon and its style from one template to a total different template (and framework version). Also it is PageBuilder related, it's no trivial task. Support is meant to be for product issues and general help.
If you produce an add on in SP Pagebuilder, you should not remove it later as this will mess up all upgrades.
As far as I can see, nothing has been removed. The "Fancy Image Link" is a special AddOn variant shipped with/for the "Glamour" template. I have the v1.5 template and the AddOn is in place. It comes with a special styling. This styling is bound with the template style and design.
Is there any issue with the latest PageBuilder version? Does the AddOn need a fix/update itself?
In the same way as the search issue should be made to work in all versions
Sure Helix2 is not the latest and greatest, but it is still maintained. Official support has not dropped. I guess it should work until J!4 is released. Regarding the global Search: IMHO, this is a minor cosmetic issue. The highlight CSS style was missing... And the recent J!3.7.x issue with the title highlight, was caused by the Joomla core changes! Obviously, this could need a quicker fix, but as mentioned earlier: Probably it simply slipped through. The staff might focus on current Helix3, and upcoming Helix and PageBuilder releases. Frankly, I can understand that not so crucial an older stuff might get lost in the daily business. This is no excuse, I just want to point out, that there was no crucial bug or something that breaks the site or compatibility.