Include repo name in issue template component dropdown

[rhcarvalho]

Extracted from a side comment on #5

having to select "Product or component" made me wonder where the issue would end up

While filing an issue in a hexpm-owned repo I thought there was some automation in place to auto-route issues from one repo to another. After looking at the diff of #4, I'm tempted to believe there is not, and the selection is only informational.

From the perspective of filing new issues, I found that experience off putting, too many form fields to go through.
If that is genuinely helping maintainers with the routing, then my suggestion is to include the intended repos next to each component.

Example

       options: 
         - Hex.pm website or API (hexpm/hexpm)
         - Hex CLI (hexpm/hex)

Affected dropdowns

.github/.github/ISSUE_TEMPLATE/bug_report.yml

Lines 9 to 24 in 7a25166

	- type: dropdown
	id: component
	attributes:
	label: Product or component
	description: Where did the issue occur? This helps us route reports filed in the wrong repository.
	options:
	- Hex.pm website or API
	- Hex CLI
	- HexDocs hosting, rendering, or search
	- Package preview
	- Version diff
	- Bob or package builds
	- Infrastructure
	- Other
	validations:
	required: true

.github/.github/ISSUE_TEMPLATE/documentation.yml

Lines 9 to 20 in 7a25166

	- type: dropdown
	id: documentation-type
	attributes:
	label: Documentation type
	description: Which documentation is affected?
	options:
	- Hex.pm documentation
	- HexDocs hosting, rendering, or search
	- Package-authored content (report this to the package repository)
	- Other
	validations:
	required: true

.github/.github/ISSUE_TEMPLATE/feature_request.yml

Lines 9 to 24 in 7a25166

	- type: dropdown
	id: component
	attributes:
	label: Product or component
	description: Which product or component would this improve?
	options:
	- Hex.pm website or API
	- Hex CLI
	- HexDocs hosting, rendering, or search
	- Package preview
	- Version diff
	- Bob or package builds
	- Infrastructure
	- Other
	validations:
	required: true

.github/.github/ISSUE_TEMPLATE/question.yml

Lines 9 to 24 in 7a25166

	- type: dropdown
	id: component
	attributes:
	label: Product or component
	description: What is your question about?
	options:
	- Hex.pm website or API
	- Hex CLI
	- HexDocs hosting, rendering, or search
	- Package preview
	- Version diff
	- Bob or package builds
	- Infrastructure
	- Other
	validations:
	required: true

[ericmj]

Yes, please add the intended repo to the dropdown 👍