Attach module and documentation artifacts to GitHub Release

[MariusStorhaug]

Context

When a new version of a PowerShell module is released via Process-PSModule, a GitHub Release is created with release notes. However, the built module artifact and documentation artifact are not attached to the release.

Request

The documentation and module build artifacts should be attached to the GitHub Release as downloadable assets. This allows users to download specific versions of the module directly from the release page.

Acceptance criteria

• The built module artifact (.nupkg or module folder) is attached to the GitHub Release
• The documentation artifact is attached to the GitHub Release
• Assets are named clearly and consistently
• Existing release creation behavior is not affected

---

Technical decisions

To be determined during implementation planning.

---

Implementation plan

• Identify the artifacts produced by the build and documentation steps
• Add a step to upload artifacts to the GitHub Release after creation
• Define naming conventions for release assets
• Test with a release that includes both module and documentation artifacts

[MariusStorhaug]

Restructured issue description into the standard three-section format.

• Rewrote from a one-line description into a proper context/request structure
• Updated title to imperative mood (removed emoji prefix)
• Added acceptance criteria and implementation plan with 4 tasks
• Applied Minor label (new feature)