Allow for flexible model notebook Naming convention

[jp-vanheerden]

The project should allow for a flexible pattern based naming convention for generated notebooks. For the example below, where the project is Investment the transformation stage is raw_to_conformed and the model is asx_contituents, the generated notebook should be:

NB_raw_to_conformed_asx_contituents

[grantkriegerai]

Duplication of issue 26

[JacquesInsight]

In discussion with @jp-vanheerden JP he mentioned that the 1st prize would be to have the ability to define a pattern but would settle for a "prefix" like "NB_"

Naming Example:

The script names are currently being read from "node_id" in the sql string passed to the Livysession.py script "LivyCursor" class.

Sample of sql:

From discussions with @insightgrantkrieger this is something that is controlled by "internal" code from the dbt adapter.