Make catalogWatchTaskScheduler/configWatchTaskScheduler more sophisticated

This issue related to #146. A fix provided there is not suitable.
For example:

1. The consul is disabled for a local environment and my own configuration for TaskScheduler with 2 threads works well.
2. The consul is enabled for PROD configuration and there is a single scheduling thread as a result.

To fix this a spring-vault approach with TaskSchedulerWrapper can be used
https://github.com/spring-projects/spring-vault/blob/main/spring-vault-core/src/main/java/org/springframework/vault/config/AbstractVaultConfiguration.java#L324

The advise in the documentation is not very good:

The watch uses a Spring TaskScheduler to schedule the call to consul. By default it is a ThreadPoolTaskScheduler with a poolSize of 1. To change the TaskScheduler, create a bean of type TaskScheduler named with the ConsulConfigAutoConfiguration.CONFIG_WATCH_TASK_SCHEDULER_NAME constant

1. It doesn't work. It needs to enable bean overriding.
2. Why I have to add to my application configuration a bean with a wired name, just to have multiple threads in the TaskScheduler?

The simplest workaround is not to use a bean with the same name, but @Primary on the application configuration.

    @Primary
    @Bean(name = "app-scheduler-pool")
    public TaskScheduler appSchedulerPool() {
        ThreadPoolTaskScheduler threadPoolTaskScheduler = new ThreadPoolTaskScheduler();
        threadPoolTaskScheduler.setPoolSize(THREADS_COUNT);
        return threadPoolTaskScheduler;
    }

Read ConsulConfigAutoConfiguration and compare its scheduler selection with the Spring Vault TaskSchedulerWrapper approach linked in the issue. Verify the documented TaskScheduler customization and @Primary configuration behavior; done means the watcher can use the application's configured scheduler without requiring the named-bean workaround.