Remove Weekly DevDB Build Workflow

[mbh329]

Addresses an issue we identified in #623.

Notes:

• The Github Actions were erroneously exporting data that would overwrite production builds in DO making it impossible to archive and QAQC any of our prior builds. We realized there was an issue because our QAQC app didn't have any data related to the 22Q2 production release of DevDB.
• This PR is meant to get rid of the weekly build of DevDB that was used by Te for (a now deprecated Dashboard he used for QAQC) and any exports related to outputting to the HED Build Engine
• I would like some feedback if we think this is overkill but I think simplifying the "test" workflow as much as possible where the Action has to be triggered directly by the engineer is a better practice than what we had in the past.
• Here is the successful build of DevDB using the test.yml

FYI

• We still have the outstanding issue that we don't have a properly archived version of 22Q2 in edm-publishing/db-developments/main/22Q2 but we do have a published version of the key database files on Bytes. The difference in these are that the version available on Bytes are just the key files including a final CSV of Housing and Dev DB along with associated Shapefiles while the files on Digital Ocean have the all important QAQC csv's and aggregate tables. To get around (a part of) the issue of the overwritten outputs for 22Q2, I manually uploaded a version of 22Q2's qaqc_historic.sql which is needed for the QAQC app to compare version of DevDB production builds

Happy to chat about this

[damonmcc]

@mbh329 you mentioned you marked the PR as a draft to get feedback before merging, but it seems like usually

• Draft PR = "I'm working on this, don't review this code yet, it's not ready to be merged"
• Ready for review PR = "I'm done working on this, review this code, it's ready to be merged"

I just noticed I can't leave comments on specific lines of code, I think cuz it's a Draft PR

[mbh329]

@damonmcc Fixed, sorry for the confusion on that one

[damonmcc]

@mbh329 I was gonna suggest changing the action's title since it isn't only used for testing, but I realized that makes it hard to compare to past runs in the Action page of the repo. usually a new name creates a separate section in the menu on the left side of that page