Patch for Honeybadger error

[maureensturgeon]

This is an alternative solution to #43023.

In the solution presented in #43023, I added additional logic to determine the primary sublevel given the hashes of data. This complicates the overall logic and decreases maintainability for an error that doesn't occur very often. The new solution presented here does not add much additional logic, the downside is that users may be able to see the bug manifested in unexpected state of a bubble choice parent bubble.

Links

• jira ticket: LP-2048

Testing story

Deployment strategy

Follow-up work

Privacy

Security

Caching

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked

[jamescodeorg]

I think it's a good idea to go with this simpler patch for now and revisit the more costly fix if we continue to get feedback on it. I'm also hoping that we'll get to rework the logic for the section progress table substantially in the next year which will give us another opportunity to address this. Thanks for taking another pass at this!