sync dev and main

[andybeet]

PRs into dev contained all necessary info. They have already been approved.
Please provide the information below so main can be synced with dev:

List PRs

List the PRs that were merged into dev that will be pulled into main and any issues they fix:

• PR !Feature(#82) replace deprecated data with MDEB datasets #83 which fixes Remove deprecated data sets #82
• PR Build(#90): Update actions in workflows for Node.j 24 #91 which fixes [Build]: workflow update to support Node.js 24 #90
• PR Chore(#88): Remove all references to gitleaks  #89 which fixes Remove gitleaks #88
• PR Chore(#68): Add development guidelines #86 which fixes Add dev guidelines and format repo #68
• PR Build(#81): Workflow to pull and update data on a schedule #87 which fixes Cron job for updating mdeb data #81
• PR Chore(#92): Changed data source from MDEB to MDAT  #94 which fixes MDEB changed to MDAT #92

Types of changes

What types of changes does this pull request introduce? Put an x in the boxes that apply.
This will inform the new release number.

• Fix (non-breaking change which fixes a bug)
• Feature (non-breaking change which adds or changes functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other change (if none of the other choices apply)

Reviewer instructions

The underlying PRs should have been reviewed. Please check that the proposed merge is correct before approving.
If any checkboxes other than "Other change" have been selected a new release is required. Please check that the following file changes are correct (a check indicates they have been edited):

• NEWS.md - add release notes
• DESCRIPTION - increment the version number according to Semantic Versioning

Note: Only changes to code, data, and doumentation constitute a versioned release. Workflows, templates etc, do not.

[andybeet]

if this looks good, after you've reviewed it and are ok merging it, i'll create a new release.
We can then run a workflow dispatch, and see if any datasets are updated and whether a pull request automatically gets generated

[jmhatch]

For the changes related to my PR, everything looks good. I didn't review the other changes, assuming they were reviewed in their initial PRs.

Made some minor edits to comments in documentation that I initially missed.