Use dry-initializer if you want that convenience, but you can also just build your own initialize methods by hand, either is fine :)
What I'm saying is that dry-initializer lets you build any sort of initializer you want. What determines compatibility with auto inject is the design choices you make, not the particular code you use to back that up.
I would suggest not using dry-initializer until at some point you really feel a need for it.
Because at least then you're not running the risk of conflating the tools and the class design.