Considering dropping Job and Message traits

[geofmureithi]

Hey everyone,

I am thinking about making a change in the next version of apalis by getting rid of the Job and Message traits. These traits don't really add much value (apart from a namespace) and can make working with apalis a bit less ergonomic.

Right now, the Job trait looks like this:

trait Job {
    const NAME: 'static str;
}

Instead, I am considering using a namespace passed to WorkerBuilder. This should simplify things and make the API more intuitive.

For example, In PR #249, there was a discussion about the need for a dynamic queue name for tests. This highlighted some limitations with the current approach, where static queue names can lead to jobs being mixed up when running tests concurrently. By removing these traits and introducing a namespace, the aim to provide a more flexible and robust solution.

I would love to get your feedback. How do you think this change will impact your use of apalis? Any potential issues or suggestions?