BUG-5222: offload XSQLBluePrint creation to first access
Constructing XSQLBluePrint in onGlobalContextUpdated() slows
down startup and is utterly inefficient (like all of XSQL).
As a stop-gap measure move its instantiation to first use,
when it is constructed from saved SchemaContext reference.
Also remove uneeded elements field, as it is not used anywhere
and just gets in the way.
Change-Id: I954d2217da6ec8b12d0b980d864cf3d776df78cc
Signed-off-by: Robert Varga <rovarga@cisco.com>
(cherry picked from commit
d0dc66335889ecec5dbc962a8604c3df96eca758)