Improve report sections and avoid regenerating existing files

[oree-xx]

Fixes

Description

1. Added prefix to determine sections and entry better.
2. Improved the update_readme function to insert report sections in alphabetical order.
3. Updated the check_for_data_files function to check if processed files have been generated previously to avoid regeneration by listing all file paths under constants and calling function in main().
4. Defined the section_order function to list all report path.
5. Added the parser argument --force to enable regenerating of processed files during testing.

Checklist

• I have read and understood the Developer Certificate of Origin (DCO), below, which covers the contents of this pull request (PR).
• My pull request doesn't include code or content generated with AI.
• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the default branch of the repository (main or master).
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated unit tests and/or test scripts for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no
  visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

[TimidRobot]

I think you can leave the files with their original name, except notes.py which can be renamed zzz-notes.py to ensure it is last.

[oree-xx]

@TimidRobot I worked on the updatereadme function, it inserts the sections in an order. I just have a little issue with what I pushed to this PR. I am trying to resolve that.

[TimidRobot]

Good work here! Please also update the PR description and title to better represent all of the work now included.

[TimidRobot]

@oree-xx Please ensure all of the report scripts are executable (-rwxr-xr-x or 0755).

See also: File permissions — Foundational technologies — Creative Commons Open Source

[TimidRobot]

good work, thank you!