sdk automation, add module if possible, regardless of failure

[XiaofeiCao]

Description

Fix false positive: https://github.com/Azure/azure-rest-api-specs/pull/30518/checks?check_run_id=33558658451
When sdk automation fails, we need to also provide additional info, e.g. packageName if possible.

• exception case, now SDK automation will fail successfully: https://github.com/test-repo-billy/azure-rest-api-specs/pull/3563/checks?check_run_id=33638342195
• normal case, no regression: https://github.com/test-repo-billy/azure-rest-api-specs/pull/3563/checks?check_run_id=33638342195
• should also fix majority of [FEATURE REQ] sdk automation breaking change detection, output generateOutput.json even when exception occurs #42829

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[XiaofeiCao]

/check-enforcer override

[XiaofeiCao]

/check-enforcer override