Add always_raise_on_error config option

[modosc]

NOTE: all the specs pass locally but rubocop is failing on a complexity check - i'm unsure exactly how to simplify this code to satisfy rubocop without making the intent less clear. happy to hear suggestions? for now i've disabled the check around the offending method

Currently when creating a new versioned record an error is raised if the Version cannot be created - this is because #save! is used:

paper_trail/lib/paper_trail/record_trail.rb

Line 62 in 47dbc22

version.save!

However, when updating, using update_columns, or destroying a versioned record no error is raised if the Version cannot be created:

paper_trail/lib/paper_trail/record_trail.rb

Line 111 in 47dbc22

if version.save

paper_trail/lib/paper_trail/record_trail.rb

Line 301 in 47dbc22

version = versions_assoc.create(data)

paper_trail/lib/paper_trail/record_trail.rb

Line 84 in 47dbc22

version = @record.class.paper_trail.version_class.create(data)

This pr adds a always_raise_on_error global config option. When set, all of the above failures will raise an error.

Fixes #1449

Thank you for your contribution!

Check the following boxes:

• Wrote good commit messages.
• Feature branch is up-to-date with master (if not - rebase it).
• Squashed related commits together.
• Added tests.
• Added an entry to the Changelog if the new
  code introduces user-observable changes.
• The PR relates to only one subject with a clear title
  and description in grammatically correct, complete sentences.

[modosc]

this was necessary because i couldn't run appraisal locally with ruby-3.2.2 - i think this fix is what got it working again

[github-actions]

This PR has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
If this is something you are committed to continue working on, please address any concerns raised by review and/or ping us again.
Thank you for all your contributions.

[modosc]

is there any chance of getting this looked at? silently not saving version data is a pretty serious issue imho.

[github-actions]

This PR has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
If this is something you are committed to continue working on, please address any concerns raised by review and/or ping us again.
Thank you for all your contributions.