Store resolved node names in manifest

[jtcohen6]

Description

A neat wrinkle:

Currently, dbt doesn't store what the database form of a node should look like as a string when it runs. That means that given an existing manifest, the best we can do with the existing manifest is to tell you what the stored node would have been, if you loaded it with the current project's config - in particular, quoting.

That's probably too restrictive! Instead, we should add a field to compiled nodes that indicates what the node's "resolved name" is. I'm pretty sure this can be filled in at compile-time, with something like str(adapter.Relation.create_from(config, node)).

What does this get us?

• Better for deferral (Defer to prod manifest for partial runs #2527, Slim CI runs, via state comparison and deferred refs #2641)
• Better dbt ls output (The json output for ls should include the database representation #2643)
• dbt-docs display of relation name (we currently get quoting wrong)
• Future work around identifying orphaned database relations (Feature: dbt compare subcommand #1135)

[jtcohen6]

Something obvious in hindsight, after playing around with #2837: relation_name is only available after a compile step, as in dbt compile, dbt docs generate, or a dbt run/dbt test of a specific model.

dbt ls doesn't include a compile step. I'll need to rethink how we'd intended to leverage this to resolve #2643. Maybe it requires a new optional argument, dbt ls --compile.