New branch creation for MicroProfile 7.1 API Tutorial

[ttelang]

@Emily-Jiang - Please request/create a new branch named v7.1 in the repo: (https://github.com/microprofile/microprofile-tutorial), I would start creating PRs with the updated MicroProfile 7.1 API Tutorial content on this new branch for everyone to review.

[ttelang]

We should create separate branches for each released version rather than using the main branch for the latest work.

Maintaining version-specific branches (e.g., v6.1, v7.1) has several advantages over release tags:

• Long-term maintenance: Each version can be updated independently for bug fixes, dependency updates, typos, etc., without affecting other versions.
• Release limitations: A release tag’s source code ZIP is immutable and cannot be updated later. A branch, however, allows the community to continuously evolve and improve the content.
• Clarity for developers: Developers often work on projects locked to specific MicroProfile versions. Stable branch URLs provide permanent references for compatibility.
• Parallel development: We can work on multiple versions (e.g., 7.2 or 8.0) simultaneously without disrupting stable content.
• Antora integration: Our Antora build is designed to pull from multiple branches. Using dedicated branches prevents the “moving target” problem caused by a constantly changing main branch, avoiding confusion for developers.

It would be better to use version branches (v6.1/, v7.1/) and keep the main branch only for the README and Antora configuration. This aligns with the standard approach followed by many similar projects.