Refactor ConfigListWarningNamespace
We are using a boolean to suppress warnings for particular statements
here. There are two problems here:
1. we can end up accessing the namespace after originalCtx has been
built, which is not nice, as it cannot be swept
2. we make poor use of namespace's capabilities (we just hold a boolean)
Make ConfigListWarningNamespace a global namespace, hence it end up
being hosted BuildGlobalContext, hence is always accessible.
Furthermore make the connection that a StatementSourceReference
is good enough alias for the statement, hence we can just store those,
reducing the number of places where StmtContexts can lurk.
JIRA: YANGTOOLS-1184
Change-Id: I31629f73e095301617254be30e10a695d13309ec
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>