* Add Razor Tooling Bug report issue template

- Given we're going to start providing a new Razor tooling editor experience we expect our users to hit a number of issues. To optimize their path of filing an issue we're creating a bug template for them to use. In parallel we're also working with the VS report an issue tool to gather additioanl data so we can encourage users to go the typical "report a bug" route for VS scenarios.

Fixes dotnet/aspnetcore#23551

* Addressed code review feedback.

* More feedback.

Add org to the team name

* Updating the issue template to get more detailed information

* Just a minor emoji to differentiate the bug and feature report lines from the rest

* Add template

* typo:

* Update config.yml

* Update text, remove winforms/wpf

* Added `aspnet-blazor-eng` as a code-owner for the `src/Components`

* Fixed the alias

https://github.com/dotnet/runtime/issues/1584

Except aspnet/AspNetCore-Internal.

* Adding some guidance regarding using StackOverflow in the issue template

* Update the new bounty link

Co-Authored-By: Barry Dorrans <github.com@idunno.org>

* Update .github/ISSUE_TEMPLATE/bug_report.md

Co-Authored-By: Daniel Roth <daroth@microsoft.com>

Doing this to avoid a long-standing bug in GitHub labeler action, which results in failure for the labeler for PRs from forks: https://github.com/actions/labeler/issues/12

* Added more path mappings to labels

* Update .github/labeler.yml

Co-Authored-By: Doug Bunting <6431421+dougbu@users.noreply.github.com>

* Create labeler.yml

Creating the initial label mappings

* Adding the auto-labeler workflow

Whoooooo...

I love me some SignalR but with BRT and such I need to focus my notifications :'(

Include more template baselines