Bump version to v0.23.1

[cgutman]

Description

Adds changelog for v0.23.1 and version bump for v0.23.1 release

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (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)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 6.10%. Comparing base (68c0f53) to head (b3ce30a).

Additional details and impacted files

@@           Coverage Diff           @@
##           nightly   #2452   +/-   ##
=======================================
  Coverage     6.10%   6.10%           
=======================================
  Files           86      86           
  Lines        17523   17523           
  Branches      8169    8169           
=======================================
  Hits          1070    1070           
- Misses       15413   15447   +34     
+ Partials      1040    1006   -34     

Flag	Coverage Δ
Linux	4.26% <ø> (ø)
Windows	2.04% <ø> (ø)
macOS-12	8.58% <ø> (+0.13%)	⬆️
macOS-13	7.77% <ø> (ø)
macOS-14	8.11% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 12 files with indirect coverage changes