Feature request: Support for max retries via API instead of attribute

Since Hangfire 1.8 it is possible to enqueue a job directly with a specified JobQueue without the `Queue` attribute. Would it be possible to also make an option to specify the max amount of retries so we don't have to use the `AutomaticRetry` attribute?

In my project, Hangfire is completely hidden for the rest of the application with reverse DI so that only my own background job client knows about Hangfire. The only thing currently in my way to completely make my application unaware of Hangfire is the `AutomaticRetry` attribute attribute.

Start by reviewing the existing enqueue API that accepts a JobQueue and the AutomaticRetry attribute behavior. Determine how a caller could provide a maximum retry count without referencing Hangfire attributes; done means the retry limit can be supplied through the API while preserving the expected retry behavior.

Written by the indexing model from the issue text.