Documentation for how to write Scribe-Data queries

[OkpePhillips]

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 adds a new documentation file SPARQL_QUERY_WRITING.md to the project in src/scribe_data/wikidata directory and details how to find forms for Wikidata lexemes and outlines the best practices for how to write Wikidata queries for use in Scribe-Data.

The documentation is generally based on the explanation by @andrewtavis on the project's chat platform.

Related issue

• Create documentation for how to write Scribe-Data queries #395

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

[OkpePhillips]

@KesharwaniArpita and @Aeeshah1 you can now review the documentation and let me know your thoughts.
Thanks
cc: @andrewtavis

[andrewtavis]

Amazing @OkpePhillips! One thing I was thinking about this, let's remember to also link the Wikidata guide we have as a community :) If you can think of a good spot at the top, then add it by all means, or I'll also look into it in my review 😊

[OkpePhillips]

Thank you @KesharwaniArpita for the suggestion. It has been committed.

Thanks @andrewtavis for your guidance always.

[andrewtavis]

Really amazing work, @OkpePhillips, and thanks for the suggestion, @KesharwaniArpita :) Lots of further work went into this as I really wanted to make sure that this has everything we need. I also switched from Slovak to Spanish so the example is a bit easier.

Some minor notes:

• Try to keep docs clean by not including ---
  • The lines of headers are all we need
• Honestly this was the only main thing - great work!