Action(Provider)Service translates grouping Action path incorrectly

The APIs involved in servicing Actions on binding level do not behave correctly when action is defined in a grouping context – i.e. for a construct like this:

grouping foo {
  container foo {
     action foo;
  }
}

container bar {
  uses foo;
}

The problem is that DOM APIs expect a SchemaNodeIdentifier, i.e. /bar/foo/foo, whereas binding-dom-adapter will translate the path to /foo/foo/foo.

Fixing this requires additional information in the binding services to disambiguate the place were the action is defined (and where the corresponding interface is generated) versus which instantiation the user wants to service.

This deficiency is flushed out by removal of ActionDefinition.getPath() and therefore is a prerequisite to adoption of yangtools-8.