Secret Snippets within projects
### Problem to solve
Secret snippets (https://gitlab.com/gitlab-org/gitlab/issues/14201) should also be possible inside projects.
### Intended users
Systems Administrator, DevOps Engineer, Software Developer
### Further details
We are using some kind of "setup scripts" per project. Some small scripts for automating server installation and configuration (install Debian packages including git, adjusting config files, and finally clone a repo from GitLab).
The scripts were called by one shell command: `wget ... | sh` on new servers.
Currently these scripts were saved as Gist on GitHub to have them hidden but still accessible for wget commands.
These scripts can be moved from Gist to GitLab Snippets as soon as https://gitlab.com/gitlab-org/gitlab/issues/14201 is done, but having the scripts inside the corresponding project would be neatly arranged.
For this, even if the project is "private", the snippet has to be "secret" for having wget access without authentication.
### Proposal
https://gitlab.com/gitlab-org/gitlab/issues/14201 provides secret personal snippets. This level would be helpful for project snippets as well.
### Permissions and Security
See https://gitlab.com/gitlab-org/gitlab/issues/14201
### Documentation
<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html
Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements -->
### Testing
<!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ -->
### What does success look like, and how can we measure that?
<!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. -->
### Links / references
https://gitlab.com/gitlab-org/gitlab/issues/14201
https://gitlab.com/gitlab-org/gitlab/merge_requests/18242
issue