fix(scheduler): resolve ambiguous RetryTemplate bean in MySQLSchedulerConfiguration

[talhadevelopes]

Problem

When using conductor.db.type=mysql with conductor.scheduler.enabled=true,
the application fails to start with:
Parameter 0 of method schedulerArchivalDAO in MySQLSchedulerConfiguration
required a single bean, but 2 were found:

• mysqlRetryTemplate
• onTransientErrorRetryTemplate

MySQLSchedulerConfiguration injected RetryTemplate by type without a
@Qualifier, causing Spring to fail when both mysqlRetryTemplate
(from MySQLConfiguration) and onTransientErrorRetryTemplate
(from ConductorCoreConfiguration) are present in the context.

Fix

Added @Qualifier("mysqlRetryTemplate") to both schedulerDAO() and
schedulerArchivalDAO() method parameters in MySQLSchedulerConfiguration.

This matches the pattern already used by every other MySQL bean in
MySQLConfiguration.java (mySqlMetadataDAO, mySqlExecutionDAO,
mySqlQueueDAO, etc.).

Changes

• scheduler/mysql-persistence/.../MySQLSchedulerConfiguration.java —
  added @Qualifier("mysqlRetryTemplate") to RetryTemplate parameter
  in both schedulerDAO() and schedulerArchivalDAO()

Fixes #1221