Restructuring of the repository tooling (#625)

* Move scripts and test-tools to tools/

* Update CHANGELOG.md

CHANGELOG.md

@@ -48,6 +48,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 - Replace genai.* nested fields with keyword array [(#608)](https://github.com/wazuh/wazuh-indexer-plugins/pull/608)
 - Check GitHub actions with dependabot [(#601)](https://github.com/wazuh/wazuh-indexer-plugins/pull/601)
 - Automatically regenerate dependant stateless modules on base module change [(#618)](https://github.com/wazuh/wazuh-indexer-plugins/pull/618)
+- Restructuring of the repository tooling [(#625)](https://github.com/wazuh/wazuh-indexer-plugins/pull/625)
 
 ### Deprecated
 -

build.gradle

@@ -21,7 +21,7 @@ apply plugin: 'java'
 apply from: 'gradle/formatting.gradle'
 
 task installLocalGitHook(type: Copy){
-    from new File(rootProject.rootDir, 'scripts/pre-commit')
+    from new File(rootProject.rootDir, 'tools/pre-commit')
     into { new File(rootProject.rootDir, '.git/hooks')}
     fileMode 0775
 }

docs/dev/run-tests.md

@@ -18,4 +18,4 @@ To run integration tests, use the `./gradlew integTest` and the `./gradlew yamlr
 
 For package testing, we conduct smoke tests on the packages using the [GitHub Actions Workflows](https://github.com/wazuh/wazuh-indexer/blob/main/.github/workflows/5_builderpackage_indexer.yml). These tests consist on installing the packages on a supported operating system. DEB packages are installed in the “Ubuntu 24.04” runner executing the workflow, while RPM packages are installed in a Red Hat 9 Docker container, as there is no RPM compatible runner available in GitHub Actions.
 
-As a last note, there is also a **Vagrantfile** and **testing scripts** in the [repository](https://github.com/wazuh/wazuh-indexer-plugins/tree/main/test-tools) to perform some tests on a real wazuh-indexer service running on a virtual machine. Refer to its README.md for more information about how to run these tests.
+As a last note, there is also a **Vagrantfile** and **testing scripts** in the [repository](https://github.com/wazuh/wazuh-indexer-plugins/tree/main/tools/test-cluster) to perform some tests on a real wazuh-indexer service running on a virtual machine. Refer to its README.md for more information about how to run these tests.

tools/test-cluster/README.md

@@ -4,7 +4,7 @@ This is an environment definition with the required configuration to be prepared
 cluster with two nodes using Vagrant and Libvirt to provision the Virtual Machines.
 
 It also generates the node's required certificates using the `wazuh-certs-tool` and copy them to each node's `/home`
-directory, leaving a copy in `test-tools/`.
+directory, leaving a copy in `test-cluster/`.
 
 ### Prerequisites
 
@@ -16,7 +16,7 @@ directory, leaving a copy in `test-tools/`.
 
 1. Navigate to the environment's root directory
    ```bash
-   cd test-tools
+   cd tools/test-cluster
    ```
 2. Initialize the environment
    ```bash

tools/test-cluster/scripts/README.md

@@ -3,7 +3,7 @@
 This is a collection of scripts aimed to facilitate the validation of the wazuh-indexer packages generated on the GitHub Action Workflow.
 
 Even if these scripts can be executed in almost any Linux environment, we expect it to be used alongside the
-Vagrant environment defined in the `test-tools`, using the scripts inside the VMs to facilitate the validation steps.
+Vagrant environment defined in the `tools/test-cluster`, using the scripts inside the VMs to facilitate the validation steps.
 
 ### GitHub token requirements