⚒🛠💣 [Bug Fix] (config + script) Fix the issue about 'git diff' of '.github/release-notes.md' and command lines of GitHub Action configuration.

[Chisanan232]

Pre-Checking

‼️Please must read this section and check by yourself.
⚠️Do NOT modify this section if it doesn't have any necessary reason.

Please verify the PR header should be satisfied below format:

[commit topic] (commit scope) <commit summary>

• commit topic: The major topic of your modify. It could have multiple topics, e.g., [Breaking Change + Test].
• commit scope: The scope in project of modify. It could have multiple scopes, e.g., (config + test).
• commit summary: Summary of the commits. It should be clear that the target, the KEY POINT why you modify it or what you resolve, etc.

Please refer to GCR (Git Commit Rules) to get more detail about it.

---

Target

• Fix the issues about CI/CD:
  • Logic problem of 'git diff' of file .github/release-notes.md.
  • Logic problem of command line in configuration of GitHub Action about searching key words in log message to verify whether it's official-release or pre-release.

Modify Code Scope

• About shell script:

  • scripts/ci/build_git-tag_or_create_github-release.sh

• About configuration of GitHub Action:

  • .github/workflows/build_git-tag_and_create_github-release.yaml

Effecting Scope

• The all automations after developers pushes their commits to GitHub platform.
  • The CI automation job about building git tag or creating GitHub release.

Description

• Add some processes in shell script:

  • git pull to get the tag info.
  • git tag to get which tag we should use to compare.

• Modify the command line in configuration of GitHub Action:

  • Modify the command line about filtering to get the final release type (official-release or pre-release).