Added documentations for how to run DAGs in development alongside how to add new documentations.

[madewithkode]

Fixes

Fixes #4356 by @AetherUnbound

Description

• This PR seeks to add a documentation on how to run DAGs in development.

• This PR also adds a new documentation on how to add new documentations.

Testing Instructions

• Start the documentation server -> just documentation/live
• Navigate to http://localhost:50230/catalog/guides/dag_testing.html to see the new documentation on running DAGs locally.
• Navigate to http://localhost:50230/meta/documentation/adding_docs.html to see the new documentation on adding new docmentation.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (just catalog/generate-docs for catalog
  PRs) or the media properties generator (just catalog/generate-docs media-props
  for the catalog or just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[AetherUnbound]

@madewithkode thank you for this awesome contribution, and for going above the issue's requirements to also add a "new documentation" page 😄 I just have a few suggestions on wording and formatting, but this is such a great PR. We really appreciate the effort you've taken here 🙌🏼

[obulat]

Thank you for very helpful instructions, @madewithkode, amazing contribution ✨

[obulat]

I guess it would be more accurate to say
"to run some DAGs locally, you might need to get the API keys from the provider and add them to the catalog/.env file". Because you can run the DAGs if you add the keys to the .env file

[AetherUnbound]

LGTM, I made one change to the formatting on the note at the end because I realized the suggestion I provided wasn't using proper MyST syntax. Sorry about that! And thanks for the contribution!