chore: rename filters.yaml to bake-filters.yaml

Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>

Author: NiccoloFei

.github/filters.yaml .github/bake-filters.yaml.github/filters.yaml renamed to .github/bake-filters.yaml

@@ -32,7 +32,7 @@ jobs:
         uses: dorny/paths-filter@fbd0ab8f3e69293af611ebaee6363fc25e6d187d # v4.0.1
         id: filter
         with:
-          filters: .github/filters.yaml
+          filters: .github/bake-filters.yaml
 
       # Compute a matrix containing the list of all extensions that have been modified
       - name: Compute matrix

.github/workflows/bake.yml

@@ -264,9 +264,9 @@ The `README.md` is typically the last file you complete. A clear, professional
 `README.md` makes an extension successful. Ensure it includes YAML examples for
 `Cluster` and `Database` resources so users can immediately adopt your work.
 
-### Add your extension to `.github/filters.yaml`
+### Add your extension to `.github/bake-filters.yaml`
 
-The `.github/filters.yaml` file is used by the CI pipeline to detect which
+The `.github/bake-filters.yaml` file is used by the CI pipeline to detect which
 extensions have been modified and need to be built, scanned, and tested.
 You must add an entry for your new extension so that changes to its directory
 trigger the testing CI pipeline.