New config refers to outdated config release version

[about-code]

Describe the bug

After having installed glossarify-md@6.2.1 when initializing a new configuration with a schema web reference, then the config refers to an older schema release version v5.1.0. As a consequence IDEs downloading the schema won't suggest the latest options that could be used with glossarify-md@6.2.1. This is an inconvenience. It's not an error and won't result in an error due to backwards compatibility.

To Reproduce

npm install glossarify-md@6.2.1
npx glossarify-md --init
{
  "$schema": "https://raw.githubusercontent.com/about-code/glossarify-md/v5.1.0/conf/v5/schema.json",
  "baseDir": "./docs",
  "outDir": "../docs-glossarified"
}

... refers to schema release version v5.1.0

Expected behavior

A newly initialized configuration should refer to the package release version:

npm install glossarify-md@6.2.1
npx glossarify-md --init
{
  "$schema": "https://raw.githubusercontent.com/about-code/glossarify-md/v6.2.1/conf/v5/schema.json",
  "baseDir": "./docs",
  "outDir": "../docs-glossarified"
}

Additional context
Existing configurations won't be updated after installing a newer package release version. This behavior can remain unchanged.