fix: close file gracefully in espsecure (ESPTOOL-804)

[gnought]

The espsecure.py script displays a ResourceWarning error regarding unclosed files when PYTHONWARNINGS="all" turns on. This issue arises because espsecure.py utilizes argparse.FileType, which opens a file handler but Python does not automatically handle the close() operation.

% PYTHONWARNINGS="all" espsecure.py sign_data --version 1 --keyfile keys.pem  --output signed.bin input.bin
espsecure.py v4.7.0
Signed 1032336 bytes of data from input.bin
/dev/.venv/lib/python3.11/site-packages/espsecure/__init__.py:1828: ResourceWarning: unclosed file <_io.BufferedReader name='keys.pem'>
  main()
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/dev/.venv/lib/python3.11/site-packages/espsecure/__init__.py:1828: ResourceWarning: unclosed file <_io.BufferedReader name='input.bin'>
  main()
ResourceWarning: Enable tracemalloc to get the object allocation traceback

This fix is to handle the close() explicitly to have a gracefully exit and avoid memory leaks.

[github-actions[bot]]

	Messages
:book:	🎉 Good Job! All checks are passing!

👋 Hello gnought, 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 :no_entry_sign: dangerJS against 2381711ebb38aa7b964823e05e4a5daab487eb21

[Honza0297]

Hello, @gnought, thank you for the contribution!

Everything looks good to me, just one nitpick: can you please squash your commits into one?

[gnought]

@Honza0297 sure, here you go.

[Honza0297]

Thank you! We will merge it once it goes through our pipeline.

[radimkarnis]

Thank you for your contribution!