feat: visibility modifiers for any module member

[lars-reimann]

Closes #1083

Summary of Changes

All module members can now have a visibility. This is useful if, say, a class is only used internally for typing.

Pipelines must always be private, which is also the default if no visibility modifier is provided. They can never be referenced anyway, not even in the same file.

[github-actions[bot]]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ JSON	eslint-plugin-jsonc	4	0	0	1.42s
✅ JSON	jsonlint	4		0	0.27s
✅ JSON	npm-package-json-lint	yes		no	0.83s
✅ JSON	prettier	4	0	0	0.8s
✅ JSON	v8r	4		0	2.37s
✅ REPOSITORY	git_diff	yes		no	0.2s
✅ TYPESCRIPT	eslint	10	0	0	5.97s
✅ TYPESCRIPT	prettier	10	0	0	1.37s

See detailed report in MegaLinter reports _Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff_

_MegaLinter is graciously provided by _

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (3f1ab6f) to head (455db1d).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1104 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 106 108 +2 Lines 20801 20816 +15 Branches 4091 4091 ========================================= + Hits 20801 20816 +15 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[lars-reimann]

:tada: This PR is included in version 0.14.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• npm package (@latest dist-tag)
• v0.14.0
• GitHub release

Your semantic-release bot :package::rocket: