[Bug]: Locating previous release also finds release assets of projects with the same name root

[ps610]

AL-Go version

probably every

Describe the issue

We have an AL-Go repository containing two projects with two apps in each project (App & TestApp). The apps of the second project depend on the apps of the first one. The roots of the project names are similar (one contains the other), which causes problems when finding the release (assets) of a previous build.
The pattern for finding the release assets consists of the project name followed by an asterisk as a wildcard. Unfortunately, this wildcard asterisk also causes release assets to be identified that actually belong to a different project that just shares the same root in its name.

Project 1: logis-interface
Project 2: logis-interface-2-core-library (depends on Project 1)

Since the projects are built independently of each other in the workflow, the second project should play no role for project 1. However, for project 1, release assets from a previous release of project 2 are also loaded:

Expected behavior

I am aware that this scenario is quite an edge case, but the restriction that project names should not overlap in their name root should at least be documented. Furthermore, a warning would be useful if there are multiple projects with the same name root.

Steps to reproduce

1. AL-Go repository with multiple projects with overlapping root in project names
2. Create a release for the repository containing both projects
3. The next build workflow for a project also finds the release assets of other projects where the project name contains the name of the project being built.

Additional context (logs, screenshots, etc.)

No response