Add correct error handling for page data nodes

[mjriley]

Technical Summary

While debugging the domain analytics issue, I noticed that the error wasn't being displayed properly in my local environment. Rather than correctly point to the missing domain property, I was instead seeing an error about origin:

I was able to add in an origin property to mimic what was being done in the Django source

However, I then realized that it would always attribute the error as occuring on the first line for unrelated code, due to incorrect position and lineno variables. The previous code cited the need to mock the token, but I believe that was due to the absence of a token causing errors. I think we should be using the real token, in order to get fully correct error information.

Once fixed, the error output aligns with normal Django expectations:

Feature Flag

No feature flag

Safety Assurance

Safety story

Verified this locally. I believe the reason we needed to fake the token was due to render_annotated's behavior when DEBUG is on. From the Django Node code, there is no exception processing unless context.template.engine.debug is True. Given that production does not run in debug mode, this change should only affect local machines.

Automated test coverage

No tests

QA Plan

No QA

Rollback instructions

• This PR can be reverted after deploy with no further considerations

Labels & Review

• Risk label is set correctly
• The set of people pinged as reviewers is appropriate for the level of risk of the change

[millerdev]

🔎 🐛

[biyeun]

i believe this is causing a lot of noise when running locally...not sure if that will be a problem on production and clogging up our sentry log limits

[mjriley]

i believe this is causing a lot of noise when running locally...not sure if that will be a problem on production and clogging up our sentry log limits

Confirmed that the issues seen are unrelated to this PR