Git action for project structure

[axif0]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

Validates src/scribe_data/language_data_extraction directory, data-type directories, and their subdirectories.
Checks for unexpected or missing sub-subdirectories based on language-specific expectations.
Fix the unstructured some of the language and data-type.

Related issue

• Add workflow to check project structure #357

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Data rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The linting and formatting workflow within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Apparently was really needed, @axif0 :) One final thing: some of the query files aren't named properly. Can we also include a check to make sure that they're all named query_...s - i.e. each should end in s :)

[andrewtavis]

I'll actually merge this now, @axif0 as we have someone who needs the paths to be valid for another part of the project 😊 Thanks so much for this! Can you send along the errors for invalid file names in another PR?

[axif0]

@andrewtavis what about the .py files? Should I skip those py file ? Or any special condition, Can you please clarify.. I was't sure earlier back then.. and forgot to ask you. Sorry again.