Maintenance: integrate utility with CI/CD release process

[dreamorosi]

Description of the feature request

Problem statement
Once all other issues related to this milestone have been completed, the new utility must be introduced in the automated release process so that it can be pushed to npm.

Summary of the feature
This unit of work tracks the activities and changes needed for the new utility to be part of the release workflow that is in charge of creating the tags and pushing the built package to npm.

Code examples
N/A

Benefits for you and the wider AWS community
N/A

Describe alternatives you've considered
None, deployment processes must be automated.

Additional context
N/A

Related issues, RFCs

#846

[dreamorosi]

Make sure this line is removed so that the API docs are generated, plus add the doc page to the nav.

[dreamorosi]

At the moment I'd be inclined to release the new utility with version number aligned with the rest of the packages (i.e. start from 1.6.0 instead of 0.0.1), but with alpha/beta/rc suffixes, i.e. 1.6.0-beta.1, 1.6.0-beta.2, etc.

I'm not sure that lerna supports applying a prerelease suffix to only one of the packages of the monorepo, so we might have to somehow handle this manually in our CI/CD.