Update issue template for new term proposal

[seokho-son]

This PR enhances the existing issue template for a new term proposal.

with following enhancements

• auto-labeling : lang/en, new term, triage/awaiting
• explain triage procedure (assessment for new term proposal)
• checklist

link to test the issue template

https://github.com/seokho-son/glossary/issues/new?assignees=&labels=lang%2Fen%2Cnew+term%2Ctriage%2Fawaiting&template=new-term.yml&title=%5BNew+term%5D+%60GlossaryTermHere%60

an opened issue example

https://github.com/seokho-son/glossary/issues/17

[netlify]

✔️ Deploy Preview for cncfglossary ready!

🔨 Explore the source changes: c4544a6

🔍 Inspect the deploy log: https://app.netlify.com/sites/cncfglossary/deploys/6228b495f3fa3b000945565d

😎 Browse the preview: https://deploy-preview-559--cncfglossary.netlify.app

[iamNoah1]

lgtm in general. Just thinking about if we add a checkbox section to also check if the term has not been rejected in the past ?!

[CathPag]

lgtm in general. Just thinking about if we add a checkbox section to also check if the term has not been rejected in the past ?!

Do we really think that people will be checking out rejected terms? I think they'll have a quick look at the open issues and submit if there isn't a term for it already. But maybe it's just me, I don't think I'd check :)

[seokho-son]

@iamNoah1 @CathPag

The first checkbox includes a link to issue list with 'new term' label and the list includes both open and closed issues. It will simply checking. List will show overall status of acceptance.

But not using 'triage/not accepted' and implying close issue action as not accepted term. is also good way.

2. Checklist
   There is no existing issue yet. (shift+click to check existing issues)

[CathPag]

In that case, LGTM :)

[iamNoah1]

lgtm