update: rc preview version support

[Koooooo-7]

By default, always use the version accurate match if it is rc version of cli, otherwise, use the major.
Provide a rc option to use the latest rc version (preview version) now and in future.

[sy-records]

The option name is too long.

[Koooooo-7]

I shorter it as rcMode, does it make sense or any idea?

[sy-records]

I recommend using --tag and -t, which can be selected as 4, 5, or rc.

[Koooooo-7]

At the very beginning I have the same thoughts of it.

docsify-cli/lib/cli.js

Line 39 in e3231a2

choices: [`${docsifyDefaultResourceVersion}`, 'rc'],

But I realized that the cli is designed to match the docsify version resources which is reasonable too.
If we provide the -tag, it means we should support all version resources generation in future, i.e. user can use cli v6 to generate v4 docsify also.
If the template or commands have incompatible change. it is hard to maintain (such as the themes).

So I think we could only provide the rc option specially for all latest rc version (cross version).
the cli of v5 provide the generation of v5 resources.
Ideally, if user wanna use v4, user needs to use v4 cli either.

[sy-records]

I think replacing the version number and adding HTML content separately are the same thing.

Generate different HTML content based on different versions and perform replacements.

--local compatible with scenarios using local docsify.

[Koooooo-7]

I think replacing the version number and adding HTML content separately are the same thing.
for instance now.

If we separated the templates/resources by versions that is feasible.
But the commands are incompatible and hard to handle.
i.e. The theme is only support vue now, If user wanna use v4 docsify, how does he use the --theme for it?