Add documentation for autolinking package names
### Problem to solve The following discussion from !37630 should be addressed: - [ ] @jramsay started a [discussion](https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/37630#note_273771451): (+3 comments) > @marcia there don't seem to be docs for this feature at all, and this was a very last minute addition. I nearly missed this community contribution. It looks like the feature was introduced in 9.3 https://about.gitlab.com/releases/2017/06/22/gitlab-9-3-released/#autolinking-package-names - we should probably create a follow up issue to add docs for this. Autolinking Rust package names was added in 12.7 without any documentation. The same functionality for Ruby, Node, Go, Python, PHP, and Objective C hasn't had docs [since 9.3](https://about.gitlab.com/releases/2017/06/22/gitlab-9-3-released/#autolinking-package-names). ### Further details <!-- * Any concepts, procedures, reference info we could add to make it easier to successfully use GitLab? * Include use cases, benefits, and/or goals for this work. * If adding content: What audience is it intended for? (What roles and scenarios?) For ideas, see personas at https://design.gitlab.com/research/personas or the persona labels at https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A --> ### Proposal <!-- Further specifics for how can we solve the problem. --> ### Who can address the issue <!-- What if any special expertise is required to resolve this issue? --> ### Other links/references <!-- E.g. related GitLab issues/MRs -->
issue