EFI: Standardize new release

### Motivation

Releasing is a lot more than just "pushing a tag".
From the previous issue (186) we would already have a standardize process using action for most of the contribution. This issue aim to define "other than publishing a package" what we want to do when a new release is rolled out, including communication / advocating but also how do we want to publish a package.
It seems manual right now, using the release feature from github can help lowering the time and effort needed to publish a new version

### Expectation

Discussus and validate way of releasing, using github release (maybe) or other solution (trying to have the lowest amount of manual operation)
Define what should be done when releasing (communication, specific update, some changes...)

### Implementation

Update documentation about releasing (process)

### Status

Part: Technical

### Draft

> Including automatic announcement + security score + perf score
With the increase of the automatic steps and to lower the workload of the contributors, building automatic releases would allow the teams to focus on more technical output.
Automatic releases announcement
Generate and update security score (scorecard and more)