fix: Fix Incorrect sed Regular Expression Handling Update tools.sh

[0xbryer]

Description

I noticed an issue with how a regular expression was used in a sed command within the bash script. Specifically, the expression:

sed 's/go*//'  

This approach has unintended behavior because the * in sed matches zero or more occurrences of the preceding character. As a result, it removes any sequence of g and o, which might not align with the intended functionality.

To address this, I updated the code to ensure it only removes the exact prefix go at the beginning of the string:

sed 's/^go//'  

Here’s the breakdown of the fix:

• Added ^ to anchor the match to the start of the string.
• Adjusted the expression to match go strictly at the beginning, avoiding accidental removal of unintended sequences.

---

Author Checklist

This correction ensures that the script behaves as expected and only removes the go prefix where necessary.

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed