Create github issue when user submits metadata

[JamesTessmer]

The goal of this PR is to add automated github issue creation.
Issues will contain:

• the submission ID
• the submitter
• the PI
• If data has already been generated
• the status of the submission
• the data types present in the submission
• the sample type
• the number of samples
• a section for notes on the submission

Current example of the output of the automation:

If data has been generated:

If no data has been generated:

[JamesTessmer]

I see the branch is failing the server check. I'm not sure if that's because of the missing token. Everything seems to be working fine when I test on my end.

[pkalita-lbl]

The changes look great!

[JamesTessmer]

The changes look great!

Great!
There are probably 1-2 minor touch ups to fix in terms of the content or formatting that I want to double check with Montana but those shouldn't affect anything.

[JamesTessmer]

@mslarae13 @pkalita-lbl
I've pushed up some new things and I think this will be the last of it.
After talking to Montana I added a new function that posts the created issue to a project board. I tried to anticipate similar fixes I had to make to the issue creation function so this one should (hopefully) be pretty close to done.
I also added 2 new variables to the .env and config to support posting an issue to a project board.

There are is also a new block of code in the issue creation to pull some IDs based on whether data has or has not been created for that submission.

I don't anticipate either of you looking at this until next week, but when you do hopefully everything is good or only requires minor fixes that can be done super quick.

[pkalita-lbl]

A couple of comments/questions based on the latest changes. Also looks like there's a conflict to resolve now, in case you hadn't seen that.

[pkalita-lbl]

Recapping a conversation with @JamesTessmer on Slack:

• James will remove the project board part from this PR since it complicates the authentication setup, and we don't want to be managing multiple personal access tokens for this.
• I will make two new issues for follow-on work:
  • Set up a new, private GitHub App in the microbiomedata org with read/write permissions for issues and projects
  • Integrate the app's private key into nmdc-server. When necessary that private key can be exchanged for an API access token which can be used for the issue creation and adding it to a project board.

[JamesTessmer]

@pkalita-lbl I've removed all the project posting related code now and it looks like everything has passed checks.
If everything looks good can you hit merge? I don't have permission to merge anything in this repo.