Fix dead links to functional testing docs (#85097)

test/functional/README.md

@@ -1,3 +1,3 @@
 # Kibana Functional Testing
 
-See our [Functional Testing Guide](https://www.elastic.co/guide/en/kibana/current/development-functional-tests.html)
+See our [Functional Testing Guide](https://www.elastic.co/guide/en/kibana/current/development-tests.html#development-functional-tests)

x-pack/README.md

@@ -53,7 +53,7 @@ yarn test:mocha
 
 #### Running functional tests
 
-For more info, see [the Elastic functional test development guide](https://www.elastic.co/guide/en/kibana/current/development-functional-tests.html).
+For more info, see [the Elastic functional test development guide](https://www.elastic.co/guide/en/kibana/current/development-tests.html#development-functional-tests).
 
 The functional UI tests, the API integration tests, and the SAML API integration tests are all run against a live browser, Kibana, and Elasticsearch install. Each set of tests is specified with a unique config that describes how to start the Elasticsearch server, the Kibana server, and what tests to run against them. The sets of tests that exist today are *functional UI tests* ([specified by this config](test/functional/config.js)), *API integration tests* ([specified by this config](test/api_integration/config.ts)), and *SAML API integration tests* ([specified by this config](test/security_api_integration/saml.config.ts)).
 

x-pack/plugins/apm/dev_docs/updating_functional_tests_archives.md

@@ -1,6 +1,6 @@
 ### Updating functional tests archives
 
-Some of our API tests use an archive generated by the [`esarchiver`](https://www.elastic.co/guide/en/kibana/current/development-functional-tests.html) script. Updating the main archive (`apm_8.0.0`) is a scripted process, where a 30m snapshot is downloaded from a cluster running the [APM Integration Testing server](https://github.com/elastic/apm-integration-testing). The script will copy the generated archives into the `fixtures/es_archiver` folders of our test suites (currently `basic` and `trial`). It will also generate a file that contains metadata about the archive, that can be imported to get the time range of the snapshot.
+Some of our API tests use an archive generated by the [`esarchiver`](https://www.elastic.co/guide/en/kibana/current/development-tests.html#development-functional-tests) script. Updating the main archive (`apm_8.0.0`) is a scripted process, where a 30m snapshot is downloaded from a cluster running the [APM Integration Testing server](https://github.com/elastic/apm-integration-testing). The script will copy the generated archives into the `fixtures/es_archiver` folders of our test suites (currently `basic` and `trial`). It will also generate a file that contains metadata about the archive, that can be imported to get the time range of the snapshot.
 
 Usage:
 `node x-pack/plugins/apm/scripts/create-functional-tests-archive --es-url=https://admin:changeme@localhost:9200 --kibana-url=https://localhost:5601`

x-pack/test/functional/README.md

@@ -1,3 +1,3 @@
 # Kibana Functional Testing
 
-See our [Functional Testing Guide](https://www.elastic.co/guide/en/kibana/current/development-functional-tests.html)
+See our [Functional Testing Guide](https://www.elastic.co/guide/en/kibana/current/development-tests.html#development-functional-tests)

x-pack/test/functional_enterprise_search/README.md

@@ -2,7 +2,7 @@
 
 ## Running these tests
 
-Follow the [Functional Test Runner instructions](https://www.elastic.co/guide/en/kibana/current/development-functional-tests.html#_running_functional_tests).
+Follow the [Functional Test Runner instructions](https://www.elastic.co/guide/en/kibana/current/development-tests.html#development-functional-tests#_running_functional_tests).
 
 There are two suites available to run, a suite that requires a Kibana instance without an `enterpriseSearch.host`
 configured, and one that does. The later also [requires a running Enterprise Search instance](#enterprise-search-requirement), and a Private API key