Setting retry strategy for Hangfire initial migration

I was wondering if it is possible to specify a retry policy to be used when Hangfire runs its initial migration on startup. Specifically, running Hangfire in an Aspire application on Apple Silicon, there is a known issue when the handshake happens with SQL Server. The workaround, also described there, is to set a retry policy. Is something like that possible with Hangfire?

Thanks,