Code of Conduct, default Issue/PR templates

[APickledWalrus]

Given our growing community spaces and presence, I have taken the time to draft a Code of Conduct for our community. The goal is to briefly describe the community we want to build, covering what behavior we want to promote, what behavior we want to avoid, and what we will do to preserve it.
better link for viewing: https://github.com/SkriptLang/.github/blob/feature/default-templates/CODE_OF_CONDUCT.md

I have also drafted generic issue and pull request templates to be used when a repository does not have one (simplifies repository management). I have attempted to strike a balance between being generic while also providing enough information for it to actually be useful across various repositories.
There are two types of issues: bug reports and suggestions. Blank issues are disabled. The pull request template is slightly modified from Skript's new template. For help/support, a link to the SkriptLang Discord is included.

Any feedback is welcome (and encouraged!)

[EquipableMC]

I don't know if this is out of scope or falls under this PR, but could we get something (like an FAQ or guide) that describes how PRs should be done for Skript (and other projects) to also help guide people that want to improve Skript and other projects? Just a thought/suggestion.

[APickledWalrus]

I don't know if this is out of scope or falls under this PR, but could we get something (like an FAQ or guide) that describes how PRs should be done for Skript (and other projects) to also help guide people that want to improve Skript and other projects? Just a thought/suggestion.

The contributing guide should cover this. Skript's is a bit outdated though. A generic one could be useful, though for the Skript repository we might want one more tailored. Regardless, it is on my list to get that updated.

[EquipableMC]

I don't know if this is out of scope or falls under this PR, but could we get something (like an FAQ or guide) that describes how PRs should be done for Skript (and other projects) to also help guide people that want to improve Skript and other projects? Just a thought/suggestion.

The contributing guide should cover this. Skript's is a bit outdated though. A generic one could be useful, though for the Skript repository we might want one more tailored. Regardless, it is on my list to get that updated.

Alright, I just did not know what fell under what lol, but good to know, thank you!

[Efnilite]

nice work pickle 🙏

[sovdeeth]

I think this is a solid base. I would like to see more elaboration on scope (i.e. applies to github, discord, etc.).

See astropy's:

This code of conduct applies to all community situations online and offline, including mailing lists, forums, social media, conferences, meetings, associated social events, and one-to-one interactions.

or Contributor Covenant's:

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

It's already covered, but I would also like some phrasing in Standards that specifically calls out being supportive and welcoming to new contributors.

Some language around proper accreditation/citation where appropriate and not plagiarizing code would also be welcome. I think Contributor Covenant v3 has a good set of standards we could pull from (and cite them at the end if we do).