Some controller RPCs do not follow NACM

[olofhagsand]

Some controller RPCs do not follow NACM data read/write rule. That is, if you can send one of those RPCs (if they themselves are not blocked via NACM) they may violate read or write NACM rules as follows:

• get-device-config, reads controller config without following NACM
• device-template-apply, reads template config without following NACM

The remaining RPC:s do not read or write controller data (or are already follow NACM), ie: config-pull, controller-commit, connection-change, transaction-error, transaction-actions-done, datastore-diff

However, an admin may want to set NACM module/rpc-name rules for these NACM as well. FOr example, controller-commit should probably have the same restrictions as commit, etc.