reward-* tags pointed at PR merge commits and statistic-* tags at the
default branch HEAD, so they became the nearest tag in git describe for
later commits. statistic-* releases were also created without
--latest=false, so the GitHub API marked them as the Latest release.
- Point new reward-* / statistic-* tags at a parentless empty-tree commit
(the merge commit SHA is kept in its message) so no branch reaches them;
tag contents and dates are read as before
- Create statistic-* releases with --latest=false
- Drop the describe-based "new commits since last statistic" check, which
cannot see detached tags; count-reward.ts already exits when there is
no reward data for the previous month
Same fix as iflytek/astron-agent#1695.
Signed-off-by: FenjuFu <92919259+FenjuFu@users.noreply.github.com>