hab plan render should provide better error messages when input template has errors

[qubitrenegade]

When input template is invalid, the resulting error message is a bit ugly.

$ cargo run -p hab plan render ./test/fixtures/render/error/consul_config.json   --default-toml ./test/fixtures/render/consul/default.toml   --user-toml ./test/fixtures/render/consul/user.toml   --mock-data ./test/fixtures/render/consul/override.json   --render-dir result --print --no-render
    Finished dev [unoptimized + debuginfo] target(s) in 0.24s
     Running `target/debug/hab plan render ./test/fixtures/render/error/consul_config.json --default-toml ./test/fixtures/render/consul/default.toml --user-toml ./test/fixtures/render/consul/user.toml --mock-data ./test/fixtures/render/consul/override.json --render-dir result --print --no-render`
» Rendering: ./test/fixtures/render/error/consul_config.json into: result as: consul_config.json

» Importing default.toml: ./test/fixtures/render/consul/default.toml
» Importing user.toml: ./test/fixtures/render/consul/user.toml
» Importing override file: ./test/fixtures/render/consul/override.json
thread 'main' panicked at 'Could not register template content: TemplateError { reason: InvalidSyntax, template_name: Some("{\n  \"datacenter\": \"{{cfg.server.datacenter\",\n  \"data_dir\": \"{{cfg.server.data-dir}}\",\n  \"log_level\": \"{{cfg.server.loglevel}}\",\n  \"bind_addr\": \"{{sys.ip}}\",\n  \"client_addr\": \"{{sys.ip}}\",\n  \"server\": {{cfg.server.mode}},\n  \"retry_join\": [\n  {{#eachAlive svc.members as |member| ~}}\n    \"{{member.sys.ip}}\" {{~#unless @last}},{{/unless}}\n  {{/eachAlive ~}}\n  ],\n  \"ports\": {\n    \"dns\": {{cfg.ports.dns}},\n    \"http\": {{cfg.ports.http}},\n    \"https\": {{cfg.ports.https}},\n    \"serf_lan\": {{cfg.ports.serf_lan}},\n    \"serf_wan\": {{cfg.ports.serf_wan}},\n    \"server\": {{cfg.ports.server}}\n  }\n}\n"), line_no: Some(3), column_no: Some(17) }', src/libcore/result.rs:1009:5
note: Run with `RUST_BACKTRACE=1` for a backtrace.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

[stale]

This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.

[stale]

This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.