Add links to the contributor guidelines in tutorials

[rwegener2]

Goal

Link current users more readily to the contributor documentation and encourage more people to consider contributing

Actions

• Add a quick section to each tutorial linking to the Contributor Guidelines page. (Ex. “Enjoying using icepyx? Consider contributing!”)

[zachghiaccio]

For Accessing ICESat-2 data tutorial:
This text is after the "Download the order" section.

Contributing to ICESat-2 Data Access

If you think the above tutorial requires more information on ICESat-2 queries, or if the querying process could be streamlined further, consider contributing to the project! More information on contributing can be found here.

---

For Subsetting ICESat-2 data tutorial:
This text is under the opening text:

Questions? Be sure to check out the FAQs throughout this notebook, indicated as italic headings. If you still have questions about the tutorial, or if you think something is missing, then consider contributing to the project through a pull request. More information on contributing can be found here.

---

For ICESat-2's Nested Variables tutorial:
This text is under the opening text:

Questions? Be sure to check out the FAQs throughout this notebook, indicated as italic headings. If you still have questions about the tutorial, or if you think something is missing, then consider contributing to the project through a pull request. More information on contributing can be found here.

---

For Visualizing ICESat-2 Elevations tutorial:
This text is under the OpenAltimetry warning:

Visualizations requiring the OpenAltimetry API are currently unavailable (since ~October 2023). The API changed and we haven’t yet updated this notebook correspondingly. Consider contributing to the project if you have ideas on how to improve visualizations or the content of this tutorial.

---

For Reading ICESat-2 Data [...] tutorial:
This text is at the very end of the page:

A developer note to users: our next steps will be to create an xarray extension with ICESat-2 aware functions (like “get_strong_beams”, etc.). Please let us know if you have any ideas or already have functions developed (we can work with you to add them, or add them for you!). If interested, then consult our Contributor Guidelines page on how to implement new ideas.

---

For ICESat-2 AWS Cloud Access tutorial:
This text is at the very end of the page:

The slow load speed is a demonstration of the many steps involved in making cloud data actionable - the data supply chain needs optimized source data, efficient low level data readers, and high level libraries that are enabled to use the fastest low level data readers. Not all of these pieces are fully developed right now, but the progress being made is exciting and there is lots of room for contribution! Any interested users may consult the Contribution Guidelines for more information.

---

For QUEST Example [...] tutorial:
This text is at the very end of the page, after the last code block:

The above workflow is performed for Argo and ICESat-2 data, and Argo is currently the only dataset implemented into QUEST. If you would like to see another dataset in QUEST, or would like to add another dataset, consider contributing! More information about QUEST contributions can be found here.

[zachghiaccio]

Above is a very long selection of possible text for each of the tutorials. I limited it to once per tutorial, but let me know if I should add more references, or put them in a different spot.