Delete the redundant blank-issue.md template

Overview

We need to delete .github/ISSUE_TEMPLATE/blank-issue.md because it duplicates the "Blank Issue Form (w/o Dependency)" issue form while applying no labels and no project board. Issues opened from it start with no size/role/feature/complexity/milestone labels and never reach CoP: DevOps: Project Board, so they are invisible to the weekly label check until someone notices by hand.

Action Items

• Delete .github/ISSUE_TEMPLATE/blank-issue.md.
• Search the repo for anything that still points at it (grep -ri "blank-issue.md" .) — the other templates, CONTRIBUTING.md, and the README are the likely places. Nothing is expected to match; this is a check, not an edit.
• After the PR merges to master, verify: open https://github.com/hackforla/devops/issues/new/choose and confirm "Blank Issue" no longer appears, while both "Blank Issue Form (w/o Dependency)" and "Blank Issue Form (w/ Dependency)" still do. This step cannot be done from the PR branch — GitHub builds the template picker from the default branch only, so the change is invisible until it merges. Don't close this issue until you have checked.

Resources/Instructions

• File to delete: https://github.com/hackforla/devops/blob/master/.github/ISSUE_TEMPLATE/blank-issue.md

• Precedent, same change in the other two repos: hackforla/devops-security#162 (merged) and hackforla/incubator#146 (open, deletes incubator's copy along with 14 other unused templates).

• The default branch here is master, not main.

• The only content unique to this file is its Action Items guidance, which the forms do not carry. Recording it here so deleting the file does not lose it — it is wanted for the in-progress work to converge all three repos on one identical pair of forms:

  If this is the beginning of the task this is most likely something to be researched and documented.

  If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task.