Added ctor overload to AutoPropertiesCommand,

because I discovered a use case for that overload, and there really was no
reason not to have that overload.
Incremented patch version,

in order to indicate that the change is mostly a very minor addition.
Actually, I was debating with myself whether adding a constructor overload
constitutes a new feature or a fix. Although the new overloads enables a
client to configure an AutoPropertiesCommand instance in a way not
previously possible, it's not really a new feature because even before
this overload, it would have been possible to derive another class from
AutoPropertiesCommand<object>, so I don't think any new capability has
been added.