Support ruby3.3 Logger by properly initialize super class

[mtasaka]

Upcoming ruby3.3 will have enhanced Logger class:
ruby/ruby@194520f which initializes newly added instance variables.
Without initializing such variables (in super class), now using subclass of Logger will cause exception.

To avoid this, first call super, then execute additional subclass initialization.

Fixes #73.

Types of changes

• 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 change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[tpowell-progress]

Hi, @mtasaka, thanks for your contribution! Responding to this and assigning to myself for visibility. Looks like a couple of CI things have to be cleaned up on our side prior to merge.

[tpowell-progress]

Hi, @mtasaka, thanks for your contribution! Responding to this and assigning to myself for visibility. Looks like a couple of CI things have to be cleaned up on our side prior to merge.

👋 @mtasaka , can you rebase against main? I trimmed out the old ruby versions and had to bumpcucumber