Add patch version release notes for 3.17.1 and 3.16.3

[josh-wong]

Description

This PR adds patch version release notes for ScalarDB 3.17 and 3.16.

Related issues and/or PRs

N/A

Changes made

• Added patch version release notes for the following versions:
  • 3.17.1
  • 3.16.3
• Updated patch versions for the className configurations in the Docusaurus configuration file.
• Changed the background color for the out-of-Maintenance-Support style.

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have updated the side navigation as necessary.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

[gemini-code-assist]

Summary of Changes

Hello @josh-wong, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the ScalarDB documentation by incorporating new patch version release notes for versions 3.17.1 and 3.16.3, available in both English and Japanese. Additionally, it includes a minor visual adjustment to the styling of the release support policy page to enhance the presentation of out-of-maintenance-support versions.

Highlights

• New Release Notes: Detailed release notes for ScalarDB v3.17.1 and v3.16.3 have been added, covering enhancements, improvements, and bug fixes for both Community and Enterprise editions in English and Japanese.
• Documentation Styling Update: The background color for the 'out-of-maintenance-support' style in the release support policy documentation has been updated for improved visual clarity.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds patch release notes for versions 3.17.1 and 3.16.3, along with their Japanese translations. It also updates the styling for versions that are out of maintenance support. The changes are mostly correct, but I have a few suggestions to improve consistency in the release notes and reduce code duplication in the CSS.