Claiming namespace dbconvert

### Namespace

dbconvert

### Ownership

- [x] The namespace is not currently owned on Open VSX

### Account Age

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

### Option 1 — VS Code Publisher with Repo

- [x] The namespace is also a publisher account on the VS Code Marketplace and has an extension published there with a repo specified in its package.json file.
- [x] The extension repo, public or private, is owned by the GitHub ID making this request (same org)

### Claim evidence

The `dbconvert` publisher on the VS Code Marketplace is ours:
https://marketplace.visualstudio.com/publishers/dbconvert

It has three extensions published, the same three published to the `dbconvert` namespace here:

| Extension | VS Code Marketplace | Open VSX |
| --- | --- | --- |
| Parquet Viewer — DBConvert | `dbconvert.dbconvert-parquet-viewer` | https://open-vsx.org/extension/dbconvert/dbconvert-parquet-viewer |
| JSONL Viewer — DBConvert | `dbconvert.dbconvert-jsonl-viewer` | https://open-vsx.org/extension/dbconvert/dbconvert-jsonl-viewer |
| SQLite Viewer — DBConvert | `dbconvert.dbconvert-sqlite-viewer` | https://open-vsx.org/extension/dbconvert/dbconvert-sqlite-viewer |

Each one declares `"repository": "https://github.com/slotix/dbconvert-streams-public"` in its
`package.json`, and that repository is owned by **slotix**, the GitHub ID making this request.

DBConvert is the product line of Slotix s.r.o.; the extensions' `homepage` points at
https://streams.dbconvert.com, which we operate. If further proof helps, I can add a TXT record
containing the URL of this issue to `dbconvert.com`, whose DNS we control.

Start by reviewing the Open VSX namespace-claim process, the linked VS Code Marketplace publisher, and the repository declaration in package.json. Done means the publisher and repository ownership evidence is verified and the dbconvert namespace claim is approved.

Written by the indexing model from the issue text.