Trigger full reparse if changes to widely used built-in macros

[jtcohen6]

There is a special category of macro that:

• dbt uses at parse time, across almost all resources in the project
• is not explicitly called within project code, such that its dependency is not grabbed during static analysis; or is excluded from depends_on.macros because of being so widely used

Those macros are:

• ref
• source
• config
• execute (?)
• generate_schema_name
• generate_database_name
• generate_alias_name

The builtins are fairly self-explanatory (though execute is a weird inclusion in those docs).

As for generate_x_name macros: The code that uses these macros is incredibly thorny, pretty old, and I think it has to do with a method named generate_generate_component_name_macro. I don't mind hard-coding that these seven need special treatment, and that any detected changes to them should be grounds for triggering a full re-parse (with logging + tracking to show for it).

Opened as a bug because this currently yields incorrect results :)

[jtcohen6]

any detected changes to them should be grounds for triggering a full re-parse

Edit: any detected changes to these macros, or any macros that these macros depend on (via depends_on.macros)