The Reqnroll plugin must be customizable

[craigfowler]

The manner in which Reqnroll plugins work means that the plugin created for Screenplay is not customizable.

For example, if I wanted to add Selenium to it, I wouldn't be able to do that. That's because I can't access the global dependencies for the container at the point I need.

This ticket is to resolve that scenario.

[craigfowler]

I might have been overlooking a really simple solution to this.

That's Reqnroll's built in customisation functionality. Whilst I won't be able to get in and customise the service container (thus Screenplay) before it's used to create a service provider, that's not actually a big deal.

BoDi permits adding new service registrations after it has been initialised. So a normal Reqnroll customisation may make changes to the container and Screenplay behaviour.

What I might do, it would be nice, is to create an extension method for the IObjectContainer interface, to get a Screenplay service collection adapter from it. This will make it easier to add additional services to the Reqnroll environment, using standard MSDI ecosystem libraries.