docs/anomaly-detection: return back absolute links instead of relative links after ce4cc4cbb2

Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/6677

Relative links in docs are much harder to maintain in consistent state comparing to absolute links:

- It is non-trivial to figure out the proper relative link path when creating and editing docs.
- Relative links break after moving the doc files to another paths, and it is non-trivial
  to figure which links are broken after that.

See also f357ee57ef , d5809f8e12 and 8cb1822b94

docs/anomaly-detection/FAQ.md

@@ -87,7 +87,7 @@ models:
     # ...
     schedulers: ['scheduler_alias']  # if omitted, all the defined schedulers will be attached
     queries: ['query_alias1']  # if omitted, all the defined queries will be attached
-    # {{% ref "./components/models.md#provide-series" %}}
+    # https://docs.victoriametrics.com/anomaly-detection/components/models/#provide-series
     provide_series: ['anomaly_score']  
   # ... other models
 
@@ -97,15 +97,15 @@ reader:
     query_alias1: 'some_metricsql_query'
   sampling_frequency: '1m'  # change to whatever you need in data granularity
   # other params if needed
-  # {{% ref "./components/reader.md#vm-reader" %}}
+  # https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader
 
 writer:
   datasource_url: 'some_url_to_write_produced_data_to'
   # other params if needed
-  # {{% ref "./components/writer.md#vm-writer" %}}
+  # https://docs.victoriametrics.com/anomaly-detection/components/writer/#vm-writer
 
 # optional monitoring section if needed
-# {{% ref "./components/monitoring.md" %}}
+# https://docs.victoriametrics.com/anomaly-detection/components/monitoring/
 ```
 
 Configuration above will produce N intervals of full length (`fit_window`=14d + `fit_every`=1h) until `to_iso` timestamp is reached to run N consecutive `fit` calls to train models; Then these models will be used to produce `M = [fit_every / sampling_frequency]` infer datapoints for `fit_every` range at the end of each such interval, imitating M consecutive calls of `infer_every` in `PeriodicScheduler` [config](./components/scheduler.md#periodic-scheduler). These datapoints then will be written back to VictoriaMetrics TSDB, defined in `writer` [section](./components/writer.md#vm-writer) for further visualization (i.e. in VMUI or Grafana)

docs/anomaly-detection/QuickStart.md

@@ -107,29 +107,29 @@ Here is an example of config file that will run [Facebook Prophet](https://faceb
 ```yaml
 schedulers:
   2h_1m:
-    # {{% ref "./components/scheduler.md#periodic-scheduler" %}}
+    # https://docs.victoriametrics.com/anomaly-detection/components/scheduler/#periodic-scheduler
     class: 'periodic'
     infer_every: '1m'
     fit_every: '2h'
     fit_window: '2w'
 
 models:
-  # {{% ref "./components/models.md#prophet" %}}
+  # https://docs.victoriametrics.com/anomaly-detection/components/models/#prophet
   prophet_model:
     class: "prophet"  # or "model.prophet.ProphetModel" until v1.13.0
     args:
       interval_width: 0.98
 
 reader:
-  # {{% ref "./components/reader.md#vm-reader" %}}
+  # https://docs.victoriametrics.com/anomaly-detection/components/reader/#vm-reader
   datasource_url: "http://victoriametrics:8428/" # [YOUR_DATASOURCE_URL]
   sampling_period: "1m"
   queries: 
-    # define your queries with MetricsQL - {{% ref "../../MetricsQL.md" %}}
+    # define your queries with MetricsQL - https://docs.victoriametrics.com/metricsql/
     cache: "sum(rate(vm_cache_entries))"
 
 writer:
-  # {{% ref "./components/writer.md#vm-writer" %}}
+  # https://docs.victoriametrics.com/anomaly-detection/components/writer/#vm-writer
   datasource_url:  "http://victoriametrics:8428/" # [YOUR_DATASOURCE_URL]
 ```