Deprication of `UseHangfireServer` in favor of `AddHangfireServer` does not allow for DB migrations to run before it

Before, using (of `Hangfire.AspNetCore`) `UseHangfireServer` would mean that I can control when the hangfire server is initialised.
This in turns allows me to create the database via migrations and apply custom schemas and permissions.
However, by depricating it in favor of `AddHangfireServer` means I can no longer do this.

I would expect the support of both.

Start by comparing the Hangfire.AspNetCore entry points UseHangfireServer and AddHangfireServer, focusing on when the server is initialized relative to database migrations and custom schema or permission setup. Confirm the expected startup ordering and whether both entry points should remain supported; done means migrations can run before the server starts.

Written by the indexing model from the issue text.