Remove issue templates

.gitlab/issue_templates/Access Request.md

-## Summary
-
-The following individuals are requesting access to this project (one per line):
-(Tag all individuals here)
-
-- Tag here
-
-The access level should be:
-- [ ] Developer access
-- [ ] Remove access
-
-Does the member need access to the VAT? (https://vat.dso.mil/vat)
-- [ ] Yes
-- [ ] No
-
-## Iron Bank Tasks
-- [ ] All accounts have been provided the necessary accesses to the projects
-- [ ] All accounts have been provided the necessary accesses to the VAT (optional)
-
-
-/label ~"Access Request::Repo" ~"CSO::To Do" ~"Owner::Ironbank"
-/cc @ironbank-notifications/onboarding
-/assign @ironbank-notifications/onboarding
\ No newline at end of file

.gitlab/issue_templates/Application - Archive.md

-## Summary
-
-Requesting this application be archived due to one of the following reasons:
-- [ ] Version is no longer supported by vendor
-- [ ] Application is End-Of-Life
-- [ ] License violation.
-- [ ] Other. See below.
-
-## Detailed Description
-
-(Please provide a detailed description of why this application should be archived)
-
-
-## Definition of Done
-- [ ] Application has been reviewed for archival
-- [ ] Project is officially marked as stale
-- [ ] Iron Bank frontend no longer lists application as available or approved
-
-
-
-
-
-/label ~"Container::Archive"
\ No newline at end of file

.gitlab/issue_templates/Application - Initial.md

-## Summary
-
-Request for a new application in Iron Bank.
-
-## Tasks
-
-Contributor:
-- [ ] Add `Dockerfile`, `hardening_manifest.yaml` and adhere to Iron Bank [requirements](https://repo1.dso.mil/dsop/dccscr/-/tree/master/Hardening)
-- [ ] Ensure container builds successfully in the Iron Bank pipeline
-- [ ] Provide justifications for findings in the [VAT](https://vat.dso.mil) ([docs](https://repo1.dso.mil/dsop/dccscr/-/blob/master/pre-approval/vat.md))
-- [ ] Open a Merge Request from your branch to `development`
-- [ ] Apply the ~"Hardening::Review" label to this issue and wait for feedback
-
-Iron Bank:
-- [ ] Merge contributor branch to `development`
-- [ ] Review findings and justifications
-- [ ] Send approval request to Authorizing Official
-- [ ] Merge `development` to `master` and close issue after approval from Authorizing Official
-
-> Note: If the above approval process is rejected for any reason, the `Hardening::Approval` label will be removed and the issue will be sent back to `Open`. Any comments will be listed in this issue for you to address. Once they have been addressed, you **must** re-add the `Hardening::Approval` label.
-
-## Questions?
-
-Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add `/cc @ironbank-notifications/onboarding`.
-
-Additionally, Iron Bank hosts an [AMA](https://www.zoomgov.com/meeting/register/vJIsf-ytpz8qHSN_JW8Hl9Qf0AZZXSCSmfo) working session every Wednesday from 1630-1730EST to answer questions.
-
-
-/label ~"Container::Initial"
-

.gitlab/issue_templates/Application - Update.md

-## Summary
-
-Request to update an application in Iron Bank.
-
-Version: (State the version you would like the application updated to)
-
-## Tasks
-
-Contributor:
-- [ ] Update `Dockerfile`, `hardening_manifest.yaml` and adhere to Iron Bank [requirements](https://repo1.dso.mil/dsop/dccscr/-/tree/master/Hardening)
-- [ ] Ensure container builds successfully in the Iron Bank pipeline
-- [ ] Provide justifications for findings in the [VAT](https://vat.dso.mil) ([docs](https://repo1.dso.mil/dsop/dccscr/-/blob/master/pre-approval/vat.md))
-- [ ] Open a Merge Request from your branch to `development`
-- [ ] Apply the ~"Hardening::Review" label to this issue and wait for feedback
-
-Iron Bank:
-- [ ] Merge contributor branch to `development`
-- [ ] Review findings and justifications
-- [ ] Send approval request to Authorizing Official
-- [ ] Merge `development` to `master` and close issue after approval from Authorizing Official
-
-> Note: If the above approval process is rejected for any reason, the `Hardening::Approval` label will be removed and the issue will be sent back to `Open`. Any comments will be listed in this issue for you to address. Once they have been addressed, you **must** re-add the `Hardening::Approval` label.
-
-## Questions?
-
-Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add `/cc @ironbank-notifications/onboarding`.
-
-Additionally, Iron Bank hosts an [AMA](https://www.zoomgov.com/meeting/register/vJIsf-ytpz8qHSN_JW8Hl9Qf0AZZXSCSmfo) working session every Wednesday from 1630-1730EST to answer questions.
-
-
-/label ~"Container::Update"

.gitlab/issue_templates/Bug.md

-## Summary
-
-(Summarize the bug encountered concisely)
-
-
-## Steps to reproduce
-
-(How one can reproduce the issue - this is very important)
-
-
-## What is the current bug behavior?
-
-(What actually happens)
-
-
-## What is the expected correct behavior?
-
-(What you should see instead)
-
-
-## Relevant logs and/or screenshots
-
-(Paste any relevant logs - please use code blocks (```) to format console output,
-logs, and code as it's very hard to read otherwise.)
-
-
-## Possible fixes
-
-(If you can, link to the line of code that might be responsible for the problem)
-
-
-## Defintion of Done
-- [ ] Bug has been identified and corrected within the container
-
-
-
-
-
-
-
-/label ~Bug
\ No newline at end of file

.gitlab/issue_templates/Feature Request.md

-## Feature description
-
-(Detailed description of the feature being requested)
-
-
-## Use cases
-
-
-(Detailed description of the use case for this feature)
-
-
-## Benefits
-
-(How does this benefit others)
-
-
-## Requirements
-
-(Any requirements for this feature to be enabled?)
-
-
-## Links / references
-
-(List of links or references that support this feature)
-
-
-## Definition of Done
-- [ ] Feature has been implemented
-
-
-
-
-
-
-
-/label ~Feature
\ No newline at end of file

.gitlab/issue_templates/Leadership Question.md

-## Leadership question
-
-(Detailed description of the question you'd like to ask the leadership team)
-
-
-
-
-
-
-
-/label ~"Question::Leadership" ~"To Do"
-/cc @ironbank-notifications/leadership
\ No newline at end of file

.gitlab/issue_templates/New Findings.md

-## Summary
-
-New findings discovered during continuous monitoring.
-
-## Tasks
-
-Contributor:
-- [ ] Provide justifications for findings in the [VAT](https://vat.dso.mil) ([docs](https://repo1.dso.mil/dsop/dccscr/-/blob/master/pre-approval/vat.md))
-- [ ] Apply the ~"Approval" label to this issue and wait for feedback
-
-Iron Bank:
-- [ ] Review findings and justifications
-- [ ] Send approval request to Authorizing Official
-- [ ] Close issue after approval from Authorizing Official
-
-> Note: If the above approval process is rejected for any reason, the `Approval` label will be removed and the issue will be sent back to `Open`. Any comments will be listed in this issue for you to address. Once they have been addressed, you **must** re-add the `Approval` label.
-
-## Questions?
-
-Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add `/cc @ironbank-notifications/onboarding`.
-
-Additionally, Iron Bank hosts an [AMA](https://www.zoomgov.com/meeting/register/vJIsf-ytpz8qHSN_JW8Hl9Qf0AZZXSCSmfo) working session every Wednesday from 1630-1730EST to answer questions.
-
-
-
-
-
-
-
-/label ~"Container::New Findings"

.gitlab/issue_templates/Onboarding Question.md

-## Onboarding question
-
-(Detailed description of the question you'd like to ask the onboarding team)
-
-
-
-
-
-
-
-/label ~"Question::Onboarding" ~"CSO::To Do"
-/cc @ironbank-notifications/onboarding
-/assign @ironbank-notifications/onboarding
\ No newline at end of file

.gitlab/issue_templates/Pipeline Failure.md

-## Summary
-
-(Summarize the pipeline issue encountered concisely)
-
-
-## Link to failed pipeline
-
-(Link to the failed pipeline)
-
-
-## What is the current bug behavior?
-
-(What actually happens)
-
-
-## What is the expected correct behavior?
-
-(What you should see instead)
-
-
-## Possible fixes
-
-(If you can, link to the line of code that might be responsible for the problem)
-
-
-## Definition of Done
-- [ ] Pipeline failure has been resolved
-
-
-
-
-
-
-
-
-/label ~Pipeline
\ No newline at end of file