move language_data_extraction under wikidata and lowercase languages

[catreedle]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have tested my code with the pytest command as directed in the testing section of the contributing guide

---

Description

This PR

• moves language_data_extraction and its contents under wikidata
• changes languages and sub-languages directory name into lowercases
• delete emoji_keywords and generate_emoji_keywords in language/sub-language directories

Related issue

• Move language_data_extraction under /wikidata and lower case all languages #446

[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]

@catreedle, sorry could you address the merge conflicts? Maybe the easiest thing to do would be to redo this PR from main and I'll make sure to bring it in before other PRs?

[andrewtavis]

We could even do a call for this at some point to make sure we're in sync?

[catreedle]

@catreedle, sorry could you address the merge conflicts? Maybe the easiest thing to do would be to redo this PR from main and I'll make sure to bring it in before other PRs?

sure, @andrewtavis. on it

[catreedle]

We could even do a call for this at some point to make sure we're in sync?

sure

[andrewtavis]

Not sure about the failed test here as it's passing locally. Let's bring this in so that other people can work from it, @catreedle :) Thanks for this!