Removal of @private and @internal comments make VSCode suggest private fields

[romaricpascal]

What

Discuss whether to ensure private and internal fields are not suggested by VSCode

Why

With the merge of the removal of comments, we removed @private and @internal JSDoc comments. This makes VSCode suggests private fields, like the SkipLink's $linkedElement in a project that consumes GOV.UK Frontend.

Who needs to work on this

Developers

Who needs to review this

Developers

Done when

• We've discussed whether to ensure private and internal fields are not suggested by VSCode
• We've created any issues (if at all) coming out of this discussion

[romaricpascal]

After discussing on Slack and a quick try that showed that even with the visibility comments in, VSCode was still suggesting private/internal fields, we're going to keep things as they are and revisit at the point we'll discuss shipping types.