Fix Stack<T> type reference

[Kissaki]

Replace incorrect reference to Stack with reference to Stack<T>.

[ghost]

Tagging subscribers to this area: @dotnet/area-system-collections
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Replace incorrect reference to Stack with reference to Stack<T>.

Author:	Kissaki
Assignees:	-
Labels:	area-System.Collections, community-contribution
Milestone:	-

[opbld32]

Learn Build status updates of commit 1d227eb:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
[xml/System.Collections.Generic/Stack1.xml](https://github.com/Kissaki/dotnet-api-docs/blob/stack-ref/xml/System.Collections.Generic/Stack1.xml)	⚠️Warning	View	Details

[xml/System.Collections.Generic/Stack1.xml](https://github.com/Kissaki/dotnet-api-docs/blob/stack-ref/xml/System.Collections.Generic/Stack1.xml)

• Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Collections.Stack`1'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[opbld30]

Learn Build status updates of commit e2a2ab0:

✅ Validation status: passed

File	Status	Preview URL	Details
xml/System.Collections.Generic/Stack`1.xml	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[gewarren]

Thanks @Kissaki