chore: remove outdated since tags from V25 components docs (#4857)

Author: web-padawan

articles/components/_input-field-common-features.adoc

@@ -105,7 +105,7 @@ Suffix elements typically don't work well with assistive technologies like scree
 
 // tag::aria-labels[]
 [#aria-labels]
-.[since:com.vaadin:[email protected]]#External & Invisible Labels (ARIA)#
+.External & Invisible Labels (ARIA)
 [%collapsible]
 ====
 Visible labels are strongly recommended for all input fields. In situations where the built-in label cannot be used, an external element can be associated as the field's label through its element `id`. Fields without any visible label should be provided an invisible label for assistive technologies like screen readers.
@@ -262,7 +262,7 @@ The helper can be rendered above the field, and below the label.
 
 // tag::borders[]
 [#borders]
-.[since:com.vaadin:[email protected]]#Borders#
+.Borders
 [%collapsible]
 ====
 Borders can be applied to the field surface by providing a value (e.g., `1px`) to the `--vaadin-input-field-border-width` CSS property. This can be applied globally to all input fields using the `html` selector, or to individual component instances. Borders are required to achieve https://www.w3.org/TR/WCAG21/#non-text-contrast[WCAG 2.1 level AA] conformant color contrast with the default Lumo styling of fields.

articles/components/_styling-section-theming-props.adoc

@@ -39,7 +39,7 @@ Style properties whose names start with `--vaadin-input-field` are shared among
 |`--vaadin-input-field-invalid-hover-highlight`
 |`--lumo-error-color-50pct`
 
-|[since:com.vaadin:[email protected]]#Background, disabled#
+|Background, disabled
 |`--vaadin-input-field-disabled-background`
 |`--lumo-contrast-5pct`
 
@@ -63,7 +63,7 @@ Style properties whose names start with `--vaadin-input-field` are shared among
 |`--vaadin-input-field-value-color`
 |`--lumo-body-text-color`
 
-|[since:com.vaadin:[email protected]]#Value text color, disabled#
+|Value text color, disabled
 |`--vaadin-input-field-disabled-value-color`
 |`--lumo-disabled-text-color`
 

articles/components/accordion/index.adoc

@@ -241,7 +241,7 @@ Details can be used instead of Accordion when there is a need to see content fro
 
 Accordions can be used to break a complex form into smaller step-by-step sections.
 
-The expandable and collapsible nature of accordions can sometimes be difficult for users to discover. Use the <<filled-panels,filled variant>> and apply [since:com.vaadin:[email protected]]##<<../tooltip#,tooltips>>## on the panels to make this more discoverable.
+The expandable and collapsible nature of accordions can sometimes be difficult for users to discover. Use the <<filled-panels,filled variant>> and apply <<../tooltip#,tooltips>> on the panels to make this more discoverable.
 
 
 == Related Components

articles/components/app-layout/index.adoc

@@ -58,7 +58,7 @@ App Layout is designed to be the application's root layout, within which most or
 
 === Flow
 
-With Flow, the root layout can be defined using the <<{articles}/flow/routing/layout#automatic-layout-using-layout,`@Layout` annotation>>, [since:com.vaadin:[email protected]]#which tells the router to render all routes or views inside of it#.
+With Flow, the root layout can be defined using the <<{articles}/flow/routing/layout#automatic-layout-using-layout,`@Layout` annotation>>, which tells the router to render all routes or views inside of it.
 
 [source,java]
 ----

articles/components/button/index.adoc

@@ -119,7 +119,6 @@ endif::[]
 Primary danger buttons should only be used when a dangerous action is the most likely action. An example of this would be the affirmative *Delete* action in a deletion confirmation dialog. Secondary and Tertiary variants can be used for actions related to current errors, such as resolving them or viewing their details.
 
 
-[role="since:com.vaadin:[email protected]"]
 === Warning Variant
 
 This is a style for distinguishing actions related to warnings: for example, in dialogs that are intended to warn the user, or to provide information that requires extra attention.
@@ -324,7 +323,7 @@ Use icons sparingly. Most actions are difficult to represent reliably with icons
 
 Icon-only buttons should be used primarily for common recurring actions with highly standardized, universally understood icons (e.g., a cross for *close*), and for actions that are repeated, such as in lists and tables. They should also include a textual alternative for screen readers using the `aria-label` attribute (see the first two buttons in the previous example).
 
-Additionally, [since:com.vaadin:[email protected]]##<<../tooltip#,tooltips>>## can be added to provide a description of the action that the button triggers (see the [guilabel]*Close* button in the previous example).
+Additionally, <<../tooltip#,tooltips>> can be added to provide a description of the action that the button triggers (see the [guilabel]*Close* button in the previous example).
 
 .Icon-Only Button Style Variant
 [NOTE]

articles/components/button/styling.adoc

@@ -148,4 +148,4 @@ Large:: `vaadin-button+++<wbr>+++**[theme~="large"]**`
 Contrast:: `vaadin-button+++<wbr>+++**[theme~="contrast"]**`
 Success:: `vaadin-button+++<wbr>+++**[theme~="success"]**`
 Danger / Error:: `vaadin-button+++<wbr>+++**[theme~="error"]**`
-[since:com.vaadin:[email protected]]#Warning#:: `vaadin-button+++<wbr>+++**[theme~="warning"]**`
+Warning:: `vaadin-button+++<wbr>+++**[theme~="warning"]**`

articles/components/card/index.adoc

@@ -3,7 +3,6 @@ title: Card
 page-title: Card component | Vaadin components
 description: The Card component is a versatile container for grouping related content and actions, with several customization options for layout and appearance.
 meta-description: The Card component is a versatile container for grouping related content and actions, with several customization options for layout and appearance.
-version: since:com.vaadin:[email protected]
 page-links:
   - 'API: https://cdn.vaadin.com/vaadin-web-components/{moduleNpmVersion:@vaadin/card}/elements/vaadin-card[TypeScript] / https://vaadin.com/api/platform/{moduleMavenVersion:com.vaadin:vaadin}/com/vaadin/flow/component/card/Card.html[Java]'
   - 'Source: https://github.com/vaadin/web-components/tree/v{moduleNpmVersion:@vaadin/card}/packages/card[TypeScript] / https://github.com/vaadin/flow-components/tree/{moduleMavenVersion:com.vaadin:vaadin}/vaadin-card-flow-parent[Java]'

articles/components/charts/charttypes.adoc

@@ -940,7 +940,6 @@ The result is illustrated in <<figure.charts.charttypes.pie.donut>>.
 [.fill.white]
 image::img/charts-donut.png[width="60%"]
 
-[role="since:com.vaadin:[email protected]"]
 [[charts.charttypes.gantt]]
 == Gantt Charts
 
@@ -2136,7 +2135,7 @@ Tree map charts have plot options type [classname]`PlotOptionsTreeMap`, which ex
 [parameter]`allowDrillToNode`:: When enabled, the user can click on a point which is a parent and zoom in on its children. Defaults to false.
 [parameter]`alternateStartingDirection`:: Enabling this option makes the tree map alternate the drawing direction between vertical and horizontal. The next level's starting direction is always the opposite of the previous. The default value is [literal]`++false++`.
 [parameter]`layoutAlgorithm`:: This option specifies which algorithm is used for setting the position and dimensions of the points. Available algorithms are defined in [classname]`TreeMapLayoutAlgorithm` enum: [literal]`++SLICEANDDICE++`, [literal]`++STRIPES++`, [literal]`++SQUARIFIED++` and [literal]`++STRIP++`. The default value is [literal]`++SLICEANDDICE++`.
-[parameter]`layoutStartingDirection`:: Defines which direction the layout algorithm starts drawing. Possible values are defined in [classname]`TreeMapLayoutStartingDirection` enum: [literal]`++HORIZONTAL++` and [literal]`++VERTICAL++`. The default value is [literal]`++VERTICAL++`. 
+[parameter]`layoutStartingDirection`:: Defines which direction the layout algorithm starts drawing. Possible values are defined in [classname]`TreeMapLayoutStartingDirection` enum: [literal]`++HORIZONTAL++` and [literal]`++VERTICAL++`. The default value is [literal]`++VERTICAL++`.
 [parameter]`levelIsConstant`:: Used together with the [methodname]`setLevels()` and [methodname]`setAllowDrillToNode()` options. When set to [literal]`++false++`, the first level visible when drilling is considered to be level one. Otherwise, the level is the same as the tree structure. The default value is [literal]`++true++`.
 [parameter]`levels`:: Set options on specific levels. Takes precedence over series options, but not point options.
 

articles/components/charts/gantt.adoc

@@ -4,12 +4,11 @@ page-title: Create Gantt Charts with Vaadin Charts
 description: Vaadin Charts support for creating Gantt charts.
 meta-description: Discover how to design and customize Gantt charts in Vaadin applications.
 order: 9
-version: since:com.vaadin:[email protected]
 ---
 
 [[charts.gantt]]
 
-= [since:com.vaadin:[email protected]]#Gantt Chart#
+= Gantt Chart
 
 A Gantt chart is a type of bar chart that can represent a project schedule. It's used for planning and scheduling projects, for displaying the start and finish dates of a project's various elements. It can help in visualizing a project's timeline, task dependencies, and progress.
 
@@ -31,7 +30,7 @@ Gantt charts are particularly useful for complex projects with multiple tasks an
 You can add Gantt chart to your application by performing the following steps:
 
 - Specify the chart type with [parameter]`ChartType.GANTT`;
-- Create [class]`GanttSeries` with [class]`GanttSeriesItems` to represent the tasks; and 
+- Create [class]`GanttSeries` with [class]`GanttSeriesItems` to represent the tasks; and
 - Then add the series to the chart.
 
 You can alternatively configure the chart using options in the [class]`PlotOptionsGantt` configuration object.
@@ -592,4 +591,4 @@ ifdef::flow[]
 include::{root}/src/main/java/com/vaadin/demo/component/charts/charttypes/gantt/GanttDragAndDropDemo.java[render,tags=snippet,indent=0,group=Flow]
 ----
 endif::[]
---
+--

articles/components/charts/usage-with-lit.adoc

@@ -56,7 +56,6 @@ include::{root}/frontend/demo/component/charts/charts-polar.ts[render,tags=snipp
 ----
 --
 
-[role="since:com.vaadin:[email protected]"]
 == Gantt Chart
 
 [.example]