Replacing markdown issue templates with yml forms

[jarmak-nv]

Description

This PR replaces the existing markdown issue templates with form-based YML templates. They provide a more interactive experience and can require certain fields be filled out prior to issue submission.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[jarmak-nv]

To see the forms in action and try them out to see what changes you may want, you can view the templates by creating issues in the feature branch:

https://github.com/jarmak-nv/cuspatial/issues/new/choose

[harrism]

Thanks for doing this. I think there are some opportunities to streamline.

[jarmak-nv]

@harrism I've added a new yml - documentation_request.yml as a possible single replacement for both of the previous doc forms. If looks good, will delete the old doc forms.

[harrism]

Just a couple more suggestions for clarity, then I approve. Would be good to get one more review.

[thomcom]

I guess I prefer two options high and low, mostly just because of decision-making pressure when working through these forms.

[jarmak-nv]

All changes incorporated aside from Thomson's good idea for the print_env.sh

Once we have that resolved, this should be good to go.

[harrism]

Can we just create an issue for print_env.sh and then get this merged independent of it?

[jarmak-nv]

I'll make the issue for it now, and will request an ops review for merge.

[thomcom]

@gpucibot merge