Fix valine & disqus meta for #1305

[sli1989]

PR Checklist

• The commit message follows guidelines for NexT.
• Tests for the changes was maked (for bug fixes / features).
  • Muse | Mist have been tested.
  • Pisces | Gemini have been tested.
• Docs in NexT website have been added / updated (for features).

PR Type

• Bugfix.
• Feature.
• Code style update (formatting, local variables).
• Refactoring (no functional changes, no api changes).
• Build related changes.
• CI related changes.
• Documentation content changes.
• Other... Please describe:

What is the current behavior?

Issue resolved: N/A

What is the new behavior?

• Screenshots with this changes: N/A
• Link to demo site with this changes: N/A

How to use?

In NexT _config.yml:

Does this PR introduce a breaking change?

• Yes.
• No.

[stevenjoezhang]

disqus also need to be modified

hexo-theme-next/scripts/filters/comment/disqus.js

Line 34 in c4796bd

<a title="disqus" href="{{ url_for(post.path) }}#comments" itemprop="discussionUrl">

[jiangtj]

@sli1989 I saw the doc https://valine.js.org/visitor.html , but its configuration is not the same as in next. Can you try using the configuration in the documentation?

文章阅读量统计 | Valine

A fast, simple & powerful comment system.

[sli1989]

I am fused about detailed programming stuffs.
For now, it works fine and intergrated in Next.
#345 was pulled by @xCss. u may ask him for this.

[stevenjoezhang]

Looks like there is no problem with valine, I think this PR can be merged