chore(cicd): fix lerna version not bumping and publishing all packages

[flochaz]

Description of your changes

0.3.1 -> 0.3.2 publication didn't bumped and published commons and tracer.

Probably a lerna issue ignoring --force-publish option. This PR remove --conventional-graduate which seems to be the option that make --force-publish option to not behave properly.

How to verify this change

Run with --conventional-graduate

npx lerna version --force-publish=\* --no-git-tag-version --no-push  --conventional-commits --conventional-graduate
lerna notice cli v4.0.0
lerna info current version 0.3.2
lerna WARN conventional-graduate all packages
lerna info Graduating all prereleased packages
lerna info Looking for changed packages since v0.3.2
lerna success No changed packages to version 

Run without it

npx lerna version --force-publish=\* --no-git-tag-version --no-push  --conventional-commits                        
lerna notice cli v4.0.0
lerna info current version 0.3.2
lerna WARN force-publish all packages
lerna info Assuming all packages changed
lerna WARN version Skipping working tree validation, proceed at your own risk
lerna info getChangelogConfig Successfully resolved preset "conventional-changelog-angular"

Changes:
 - @aws-lambda-powertools/commons: 0.3.2 => 0.3.3
 - @aws-lambda-powertools/logger: 0.3.2 => 0.3.3
 - @aws-lambda-powertools/metrics: 0.3.2 => 0.3.3
 - @aws-lambda-powertools/tracer: 0.3.2 => 0.3.3

PR status

Is this ready for review?: YES
Is it a breaking change?: NO

Checklist

• My changes meet the tenets criteria
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in areas that should be flagged with a TODO, or hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• The code coverage hasn't decreased
• I have added tests that prove my change is effective and works
• New and existing unit tests pass locally and in Github Actions
• Any dependent changes have been merged and published in downstream module
• The PR title follows the conventional commit semantics

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.