feat(catalog/gerrit): Add option to configure schedule via app-config.yaml

Relates-to: PR #13859
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>

docs/integrations/gerrit/discovery.md

@@ -32,10 +32,13 @@ const builder = await CatalogBuilder.create(env);
 builder.addEntityProvider(
   GerritEntityProvider.fromConfig(env.config, {
     logger: env.logger,
+    // optional: alternatively, use scheduler with schedule defined in app-config.yaml
     schedule: env.scheduler.createScheduledTaskRunner({
       frequency: { minutes: 30 },
       timeout: { minutes: 3 },
     }),
+    // optional: alternatively, use schedule
+    scheduler: env.scheduler,
   }),
 );
 ```
@@ -54,6 +57,11 @@ catalog:
         host: gerrit-your-company.com
         branch: master # Optional
         query: 'state=ACTIVE&prefix=webapps'
+        schedule: # optional; same options as in TaskScheduleDefinition
+          # supports cron, ISO duration, "human duration" as used in code
+          frequency: { minutes: 30 }
+          # supports ISO duration, "human duration" as used in code
+          timeout: { minutes: 3 }
       backend:
         host: gerrit-your-company.com
         branch: master # Optional
@@ -62,8 +70,8 @@ catalog:
 
 The provider configuration is composed of three parts:
 
-- host, the host of the Gerrit integration to use.
-- branch, the branch where we will look for catalog entities (defaults to "master").
-- query, this string is directly used as the argument to the "List Project" API.
-  Typically you will want to have some filter here to exclude projects that will
+- **`host`**: the host of the Gerrit integration to use.
+- **`branch`** _(optional)_: the branch where we will look for catalog entities (defaults to "master").
+- **`query`**: this string is directly used as the argument to the "List Project" API.
+  Typically, you will want to have some filter here to exclude projects that will
   never contain any catalog files.