Fix CI Errors

[jkawamoto]

This PR addresses recent CI errors. It includes the following changes:

• Removed support for Python 3.6 and 3.7 since they are deprecated.
• Tests now run on both Intel Mac (macos-13) and Apple Silicon Mac (macos-14).
• Updated mecab-python3 to support Apple Silicon and Python 3.12.
• Skipped tests with mecab-ko on Apple Silicon or Python 3.12 because it doesn’t support them yet. (Add support for Apple Silicon NoUnique/pymecab-ko#2, Python 3.12 NoUnique/pymecab-ko#8)

[martinpopel]

@mjpost @ozancaglayan Do you agree with dropping support for Python 3.6 and 3.7 (which are end of life)?
I agree because I don't see any other easy way how to prevent CI failures in future (and we cannot officially support Python versions which we don't test with CI).

[ozancaglayan]

Hi. There's no reason to keep 3.6 and 3.7 there I agree. 3.8 is also coming to EOL October 2024. We could drop that one later as well.

Thanks for the PR!

[ozancaglayan]

It would be good to do a v2.4 release probably once merged.

[mjpost]

Thanks, guys—I agree about dropping support. 2.4.2 was released a while ago; I don't think we need a new release with this PR?

[ozancaglayan]

I was looking at https://github.com/mjpost/sacrebleu/releases which shows 2.3.x as the latest.

[mjpost]

Ah, yeah, I should update that. It's a separate process. 2.4.2 is available on pypi.

[mjpost]

Actually I'm sure there's a way to do this:

• Tag a release
• Have it automatically pushed to pypi via Github action
• Have it automatically released on Github via Github action

[ozancaglayan]

I dont have time currently but yes there is:

• https://github.com/softprops/action-gh-release
• Writing a new workflow that'll be triggered for new tags
• for pushing to PyPI, we'll need to add PyPI credentials as SECRETS to the repo and you can just use the same shell commands in a run:  step