fix: stop exit 0 when being called programmatically

[hfudev]

The current esptool.main(...) call causes the Python process to exit immediately.

This PR bypassed the exitcode 0 to allow the Python code to continue running.

(blocks espressif/pytest-embedded#362)

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello hfudev, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved, we synchronize it into our internal git repository.
4. In the internal git repository we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against d8ae230

[peterdragun]

Overall LGTM, but we should also do the same thing for espefuse and espsecure.

[hfudev]

Thank you. updated. PTAL again.

[peterdragun]

LGTM, thank you for the update.

[dobairoland]

@hfudev Thank you for this PR and looking into espressif/pytest-embedded#362. Will it be enough for you if we create a dev release with this patch, i.e. 5.1.dev1?

[dobairoland]

@peterdragun Could you please cherry-pick this into our internal repo?

[radimkarnis]

LGTM 👌

[hfudev]

@hfudev Thank you for this PR and looking into espressif/pytest-embedded#362. Will it be enough for you if we create a dev release with this patch, i.e. 5.1.dev1?

Hi @roland can we release a 5.0.3 version? I think it's more like a bugfix instead of a feature.

[dobairoland]

@hfudev Unfortunately, we already merged several features and the next release from the v5.* line will be 5.1.

[dobairoland]

@hfudev This fix is available in https://pypi.org/project/esptool/5.1.dev1/. Thanks!

[hfudev]

Thank you!