migrate seone function in theme hook

[robinallezard]

SEOne commit relative

[anoziere]

The decoupling goal makes sense, but the migration is partial and there is a site-wide title regression.

• base.html.twig still opens with {% set breadcrumb = SEOneBreadcrumb() %}, an unconditional module call in the base layout. Without SEOne installed, every page fatals on an unknown function. Same problem in index.html.twig (SEOneWebSite(), SEOneWebPage(), SEOneLocalBusiness()), category.html.twig (SEOnePageH1()), the Product component, and contact.html.twig. As long as those remain, the theme still hard-depends on the module.
• The <title>{% block title %}...{% endblock %}</title> wrapper was removed from base.html.twig, but ~27 templates still define block title. Twig silently discards all of them, so no page renders a title tag anymore. The og:title/og:url/og:type/twitter meta defaults went away with it, and it's not obvious the hook side replaces them exactly.
• src/EventListener/SeoListener.php ships four empty no-op methods, subscribes to SEOnePageh1Event while importing SEOnePageH1Event (case mismatch), and assigns getCurrentRequest() (nullable) to a non-nullable readonly Request property, which will throw outside an HTTP context.
• The addPseToCart browser event and the SimilarContent exclude filter look unrelated to the SEOne migration; splitting them out would keep this PR easier to review.

Worth reviewing together with thelia-modules/SEOne#11 since the two halves have to land in a consistent state.

[robinallezard]

1er point => Seone étant dans thelia-skeleton c'est normal qu'on est un couplage fort entre le module et le theme

2ème point => corrigé avec la nouvelle stratégie du module SEOne ( solution avec theme_hook et block twig)

les autres points sont liés à d'autres corrections apporté suite à la migration de GTM et recaptcha