Fix/improve bulk index error reporting

[whatisgalen]

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Description of Change

Issues Solved

Closes #12003

Checklist

• I targeted one of these branches:
  • dev/8.0.x (under development): features, bugfixes not covered below
  • dev/7.6.x (main support): regressions, crashing bugs, security issues, major bugs in new features
  • dev/6.2.x (extended support): major security issues, data loss issues
• I added a changelog in arches/releases
• I submitted a PR to arches-docs (if appropriate)
• Unit tests pass locally with my changes
• I added tests that prove my fix is effective or that my feature works
• My test fails on the target branch

Accessibility Checklist

Developer Guide

Topic	Changed	Retested
Color contrast
Form fields
Headings
Links
Keyboard
Responsive Design
HTML validation
Screen reader

Ticket Background

• Sponsored by:
• Found by: @
• Tested by: @
• Designed by: @

Further comments

[apeters]

@whatisgalen what's the best way to test this?

[whatisgalen]

@whatisgalen what's the best way to test this?

@apeters If you manually (via postgres) save something like this to a bad nodevalue to tile.tiledata and then try to index that resource, you should be able to test this PR for whether it surfaces the specific document_parsing_exception that comes up

[apeters]

@whatisgalen Can you give me exact steps to repro this? I've tried adding "bad" data to a non-localized string datatype but I"m seeing different errors unrelated to your fix.