parse manifest documentation without rendering (some) jinja

[VDFaller]

In https://github.com/z3z1ma/dbt-osmosis, he has done a great job of making it easier to manage inheritance of documentation to allow a more DRY feeling experience. It relies on the manifest to pull the dag and information about the column descriptions and other information that should flow downstream. In z3z1ma/dbt-osmosis#129 we patched in a way to make it so doc blocks would stay doc blocks instead of using the rendered docs blocks.

But there are issues with that implementation and it's possible we want to have other things keep the jinja as they flow downstream z3z1ma/dbt-osmosis#216 (comment).

I'm wondering if it makes sense / be more performant to have a way here to exclude fields from jinja parsing them into the manifest. Something like

dbt parse --exclude-from-render "[source.database, source.table.column.description]"

Obviously we can patch specific things in dbt-osmosis. Or make our own manifest with the jinja repatched. Just don't know if there would be any other use cases where this might be useful.

Would this be a large change?