fix impl variants (#2371)

I noticed that the impl-variants behavior was not quite consistent...
some pages had an `ImplVariantsHint`, but no `impl-variants: true` and
another page (the new remote-authentication guide) had an
`ImplVariantsHint` without java or node specific sections.

=> add the hint and metadata where there are java or node specific
sections

---------

Co-authored-by: Christian Georgi <chgeo@users.noreply.github.com>
Co-authored-by: René Jeglinsky <rene.jeglinsky@sap.com>

Author: 3 people

guides/deploy/to-kyma.md

@@ -7,6 +7,7 @@ breadcrumbs:
   - Deployment
   - Deploy to Kyma
 status: released
+impl-variants: true
 # uacp: Used as link target from Help Portal at https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/29c25e504fdb4752b0383d3c407f52a6.html and https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/e4a7559baf9f4e4394302442745edcd9.html
 ---
 

guides/security/authentication.md

@@ -4,6 +4,7 @@ label: Authentication
 synopsis: >
   This guide explains how to authenticate CAP services.
 status: released
+impl-variants: true
 ---
 
 <script setup>

guides/security/authorization.md

@@ -2,6 +2,7 @@
 synopsis: >
   This guide explains how to restrict access to data by adding respective declarations to CDS models, which are then enforced by CAP's generic service providers.
 uacp: Used as link target from SAP Help Portal at https://help.sap.com/products/BTP/65de2977205c403bbc107264b8eccf4b/e4a7559baf9f4e4394302442745edcd9.html
+impl-variants: true
 ---
 
 <script setup>

guides/security/cap-users.md

@@ -4,6 +4,7 @@ label: CAP Users
 synopsis: >
   This guide introduces CAP user abstraction and role assignments.
 status: released
+impl-variants: true
 ---
 
 <script setup>

guides/security/remote-authentication.md

@@ -21,7 +21,6 @@ status: released
 
 # Outbound Authentication { #remote-authentication }
 
-<ImplVariantsHint />
 
 This guide explains how to authenticate remote services.
 

guides/services/consuming-services.md

@@ -19,6 +19,8 @@ If you want to use data from other services or you want to split your applicatio
 
 [[toc]]
 
+<ImplVariantsHint />
+
 ## Introduction
 
 If you want to use data from other services or you want to split your application into multiple microservices, you need a connection between those services. We call them **remote services**. As everything in CAP is a service, remote services are modeled the same way as internal services — using CDS.

guides/uis/fiori.md

@@ -12,6 +12,7 @@ CAP provides out-of-the-box support for SAP Fiori elements. This guide explains
 [[toc]]
 
 
+
 ## SAP Fiori Preview
 
 For entities exposed via OData V4 there is a _Fiori preview_ link on the index page. It dynamically serves an SAP Fiori elements list page that allows you to quickly see the effect of annotation changes without having to create a UI application first.

tools/apis/cds-build.md

@@ -11,6 +11,7 @@ CDS already offers build plugins to create deployment layouts for the most use c
 Build plugins are run by `cds build` to generate the required deployment artifacts. Build tasks hold the actual project specific configuration. The task's `for` property value has to match the build plugin ID.
 
 The following description uses the [postgres build plugin](https://github.com/cap-js/cds-dbs/blob/55e511471743c0445d41e8297f5530abe167a270/postgres/cds-plugin.js#L9-L48) as reference implementation. It combines runtime and design-time integration in a single plugin `@cap-js/postgres`.
+
 ## Add Build Logic
 
 A build plugin is a Node.js module complying to the [CDS plugin architecture](../../node.js/cds-plugins).