chore: Add .vscode/settings.json & extensions.json

[vorburger]

Based on https://github.com/enola-dev/enola/blob/a8efaa5b7ba9d5111fcb235baad9815e2b47dbb4/.vscode/settings.json

This makes it easier to contribute to this project using VSC.

[gemini-code-assist]

Summary of Changes

Hello @vorburger, 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 introduces Visual Studio Code configuration files (.vscode/settings.json and .vscode/extensions.json) to the repository. The aim is to streamline the development setup for contributors using VS Code, including those leveraging GitHub Codespaces, by providing recommended extensions and consistent code formatting rules.

Highlights

• VS Code Extension Recommendations: Adds a list of recommended VS Code extensions, primarily for Java development, to guide new contributors.
• Standardized VS Code Settings: Configures VS Code settings to enforce consistent code formatting (e.g., formatOnSave, trimTrailingWhitespace), set up Google Java Format, and optimize Java development experience within the IDE.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 introduces VS Code settings to standardize the development environment for this Java project. The changes include recommended extensions and workspace settings for formatting, import organization, and other Java-specific configurations. My review focuses on ensuring these settings are correct and follow best practices. I've identified an issue with the configured import order and suggested a correction to align with standard Java conventions, improving consistency for all contributors.

[Poggecci]

re-approving to trigger import