release 1.0.0

[kenhuang]

Description

• 1.0.0 release
• added release commands
• remove prefix v in tags

  
  ➜ bbs-signatures git:(kh/release-1.0.0) git push origin --tags
  Enumerating objects: 1, done.
  Counting objects: 100% (1/1), done.
  Writing objects: 100% (1/1), 169 bytes | 169.00 KiB/s, done.
  Total 1 (delta 0), reused 0 (delta 0)
  To github.com:mattrglobal/bbs-signatures.git
  * [new tag]         0.1.0 -> 0.1.0
  * [new tag]         0.2.0 -> 0.2.0
  * [new tag]         0.3.0 -> 0.3.0
  * [new tag]         0.4.0 -> 0.4.0
  * [new tag]         0.5.0 -> 0.5.0
  * [new tag]         0.6.0 -> 0.6.0
  * [new tag]         0.7.0 -> 0.7.0
  * [new tag]         1.0.0 -> 1.0.0

- [x] Tests for the changes have been added (for bug fixes / features)
- [x] The commit message(s) follow [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/)
- [x] Documentation has been added / updated (for bug fixes / features)
- [x] Changes follow the **[contributing](../docs/CONTRIBUTING.md)** document.

## Motivation and Context

<!--- Why is this change required? What problem does it solve? -->

## Does this PR introduce a breaking change?

- [ ] Yes
- [x] No

<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->

## Which merge strategy will you use?

<!-- This indicates to reviewers whether they need to check your commits are ready to be rebased on master or not. -->

- [ ] Squash
- [x] Rebase (REVIEW COMMITS)

[tplooker]

@kenhuang approved, to release can you rebase this locally and push to master, otherwise the tags get messed up

[kenhuang]

@kenhuang approved, to release can you rebase this locally and push to master, otherwise the tags get messed up

sure, will do rebase merge to keep the tag info.