Build(#81): Workflow to pull and update data on a schedule

[andybeet]

Justification

To prevent R package data drifting from the MDEB data on the GIS Hub a workflow is created to pull the MDEB data into the package on a schedule. The workflow will create a pull request off dev if any changes were found. This will need to be manually reviewed and merged

Fixes #81

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)

Further comments

The workflow is currently set at weekly. Might be good to see how it is working or failing before we set it to monthly or quarterly. A workflow dispatch has also been added to the workflow enabling us to run the workflow manually at any point in time. Currently a PR is created. After some time we could automate the commits to the repo and auto generate a release of the package

Reviewer instructions

Unfortunately, until the workflow is in the main branch i dont think you can test it. As an alternative you could fork the repo, merge this branch into main and test it there. Please look over the yml and comment below.