Aliased Resolver/Mutation should be registered even when not on auto mapping

[renatomefi]

Q	A
Bug report?	no
Feature request?	yes
BC Break report?	yes
RFC?	no
Version/Branch	0.10.0

Currently the only way to use the AliasedInterface is if you use the auto mapping feature, I suggest to split this in two moments:

• One pass takes care of the auto mapping and set the tags automatically
  • This one can be specially turned off when using SF 3.3+ by doing:

    App\Resolvers\:
        resource: '../src/Resolvers'
        tags: ['overblog_graphql.resolver']

• The second pass will then find all services with the resolver or mutation tags and then check for the AliasedInterface thus changing its definition to support it

[renatomefi]

Awesome, thanks @mcg-web