Update automated tools workflow to be deterministic for the same set of tools

[princerajpoot20]

We have recently made a change in our automated tools workflow to add a manual approval step by a maintainer before merging tool-related PRs.
We introduced this step as a safety measure. Previously, this tool data was directly fetched from the Github API and displayed on our website under the tools section. There was no human intervention, and PRs were auto-approved by a bot. We changed this from auto-approval to manual approval by a maintainer because it is simply not safe. Someone could exploit this flow and publish anything or any text on our website. It could include abusive content. To avoid this, we introduced manual approval. The maintainer quickly checks whether everything is good before merging.

While reviewing these PRs, I found cases like #5321 where there is actually no real change, only a reordering of tools. This might be happening because of the order in which we receive responses from the API.

Hence, we should find out a way to make this flow is deterministic. If we have the same set of tools, we should find a way to make the ordering consistent so that these unnecessary diffs do not appear in PRs. This will make PR reviews quicker for maintainers.
Currently, this does not seem problematic, but when we combine reordering changes with actual updates (for example, when a new tool is introduced), it increases the PR review burden. This workflow runs on a weekly basis, hence, we should try to improve it.

[manja316]

I'd like to work on this issue. Here's my implementation plan:

Root causes identified:

1. extract-tools-github.ts — The GitHub Code Search API returns results in non-deterministic order across runs. The Set used to collect items preserves this random insertion order.
2. tools-object.ts — Promise.all(data.map(...)) processes tools concurrently, and push() calls into toolsList happen when each HTTP request resolves — the completion order varies between runs.
3. combine-tools.ts — languageList and technologyList are built via push() in encounter order. When tools are processed in a different order, newly discovered tags appear at different positions.

Fix:

1. Sort GitHub API results by repository.full_name (stable key) after collection
2. Sort each category's toolsList by title after Promise.all completes in convertTools()
3. Sort languageList and technologyList by name before writing to all-tags.json

Note: combine-tools.ts already sorts the final tools.json toolsList by title (line 282), so the main remaining non-determinism is in tools-automated.json and all-tags.json.

I have a working implementation with all existing tests passing + a new deterministic ordering test.

[princerajpoot20]

Everyone, this issue is under Microgrant program, please refrain working on it. Please refer to the rules of program here: https://github.com/asyncapi/community/blob/master/docs/010-contribution-guidelines/BOUNTY_PROGRAM.md