Parse project name for issue key

[supremebeing7]

Some users workflow has them putting the issue key in the project name. We should be able to parse the issue key out of the project as well. However, we should support the workflow that has users putting the issue key in the description as well, and we should control for multiple different keys in different places

The issue key priority should be:

• description
• project name
• mapping file