Claiming namespace grounder

### Namespace

grounder

### Ownership

- [x] The namespace is not currently owned on Open VSX (verify by a search on [open-vsx.org](https://open-vsx.org))

### Account Age

- [x] The GitHub ID making this request has at least 12 months of public history

### VS Code Publisher with Repo

- [ ] The namespace is also a publisher account on the VS Code Marketplace (check by browsing https://marketplace.visualstudio.com/publishers/{publisher}) and has an extension published there with a repo specified in its package.json file.

### VS Code Publisher without Repo

- [x] The namespace is also a publisher account on the VS Code Marketplace and does not have published extensions or has published extensions with no GitHub repos.

### Not a VS Code Marketplace Publisher

- [ ] The namespace is not a publisher account on the VS Code Marketplace

### All Other Cases

- [ ] You are unable to provide the inputs required in the three options above. This option will take the longest to process.

### Claim evidence

Open VSX namespace: grounder (created, contributor only, not owned)
VS Code Marketplace publisher: grounder (created, no extension published yet)
GitHub: https://github.com/andrej-kolic (account since 2012)
Repo that will ship the extension: https://github.com/andrej-kolic/grounder
Granted temporary Reader on the Marketplace publisher to 46461f8e-a0a8-6de8-9186-8ac72e28656d

Start by verifying the grounder namespace on open-vsx.org and the grounder publisher on the VS Code Marketplace using the links in the checklist. Confirm the GitHub account, repository, and temporary Marketplace Reader access; the work is done when the namespace ownership request is processed.

Written by the indexing model from the issue text.