[FW][FIX] config: Fix the action version extractor

[fw-bot]

the tool 'parse_message' was using an incorrect regex to capture the version of the release. It specifically pose problem with the master release for which the alpha tag was not considered, implying that 2 consecutive master release would have the same tag, which crashes and ultimately prevent further steps of the github action, like the publication on NPM.

We can rather rely on the information of the package.json file since it's properly updated.

Description:

description of this task, what is implemented and why it is implemented that way.

Odoo task ID : TASK_ID

review checklist

• feature is organized in plugin, or UI components
• support of duplicate sheet (deep copy)
• in model/core: ranges are Range object, and can be adapted (adaptRanges)
• in model/UI: ranges are strings (to show the user)
• undo-able commands (uses this.history.update)
• multiuser-able commands (has inverse commands and transformations where needed)
• new/updated/removed commands are documented
• exportable in excel
• translations (_lt("qmsdf %s", abc))
• unit tested
• clean commented code
• track breaking changes
• doc is rebuild (npm run doc)
• status is correct in Odoo

Forward-Port-Of: #2123

[robodoo]

Pull request status dashboard.

[fw-bot]

@rrahir @LucasLefevre cherrypicking of pull request #2123 failed.

stdout:

Auto-merging tools/parse_message.js
CONFLICT (content): Merge conflict in tools/parse_message.js

stderr:

08:51:09.018654 git.c:455               trace: built-in: git cherry-pick b39921e1dae3ee96bdbb9edc58e51b00d6f3feeb
error: could not apply b39921e1... [FIX] config: Fix the action version extractor
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
----------
status:

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

[rrahir]

@robodoo r+