Update mapstore submodule for version 5.0.x

[allyoucanmap]

This PR includes latest beckport from MapStore stable branch

[gemini-code-assist]

Summary of Changes

Hello @allyoucanmap, 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 integrates the latest stable updates from the MapStore project, specifically targeting the 5.0.x release series. It achieves this by updating the MapStore2 submodule to a newer commit and adjusting the @mapstore/project dependency to point to the geonode-5.0.x branch, ensuring compatibility and access to the latest features and fixes.

Highlights

• MapStore Submodule Update: The MapStore2 Git submodule has been updated to a new commit (8d9678ae60f4527310c9b3d0b3cdd05f6ee78305) to align with the 5.0.x version.
• Project Dependency Branch Change: The @mapstore/project dependency in package.json has been switched from tracking the master branch to the geonode-5.0.x branch.

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 updates the MapStore submodule and its corresponding project tooling dependency to align with the 5.0.x version. The changes are straightforward and logical. I have added one suggestion to improve build reproducibility by pinning the @mapstore/project devDependency to a specific commit hash instead of a branch name. This is a best practice for ensuring stable and consistent builds over time.

[gemini-code-assist]

For improved build reproducibility, it is recommended to pin this dependency to a specific commit hash instead of a branch name. While using the geonode-5.0.x branch is an improvement over master, the branch can still receive further updates. This could lead to inconsistencies if npm install is run at different times, making builds non-reproducible. Pinning to a commit hash ensures that every build uses the exact same version of the dependency, which is a practice already followed for the MapStore2 submodule in this same PR.