Add method to generate a globally scoped type name to Node API

[amykyta3]

A common operation in an exporter is to generate a globally unique type name for a given node that uniquely identifies a component type throughout its entire lexical hierarchy. The existing API provides the Node.inst.get_scope_path() method which is tantalizingly close to the correct solution, but does not provide the rendered type names after augmented by parameters or DPAs (See discussion in #186)

Provide a mechanism to generate a robust globally scoped type name as is done in PeakRDL-uvm's class name generation.

Be sure to also account for variants of a field definition with different widths. The spec's type uniquification semantics do not account for this.

[amykyta3]

Implemented. Will be available in upcoming 1.27.0 release