feat: Add validateLocationsExist option for the BitbucketServer entity provider

Signed-off-by: Joan Miquel Luque Oliver <joan.luque@dynatrace.com>

docs/integrations/bitbucketServer/discovery.md

@@ -66,6 +66,7 @@ catalog:
           projectKey: '^apis-.*$' # optional; RegExp
           repoSlug: '^service-.*$' # optional; RegExp
           skipArchivedRepos: true # optional; boolean
+        validateLocationsExist: false # optional; boolean
         schedule: # same options as in SchedulerServiceTaskScheduleDefinition
           # supports cron, ISO duration, "human duration" as used in code
           frequency: { minutes: 30 }
@@ -86,6 +87,10 @@ catalog:
     Regular expression used to filter results based on the repo slug.
   - **`skipArchivedRepos`** _(optional)_:
     Boolean flag to filter out archived repositories.
+- **`validateLocationsExist`** _(optional)_:
+  Defaults to `false`.
+  Whether to validate locations that exist before emitting them.
+  This option avoids generating locations for catalog info files that do not exist in the source repository.
 - **`schedule`**:
   - **`frequency`**:
     How often you want the task to run. The system does its best to avoid overlapping invocations.