chore: Bump version to v1.0.0

[LeeDongGeon1996]

Description

• +semver: major not worked before v1.
• https://gitversion.net/docs/reference/version-increments
• https://github.com/GitTools/GitVersion/issues/1539

Checklist

• [x] My code follows the existing style, code structure, and naming taxonomy
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have performed a self-review of my own code and included any verifying manual calculations
• [x] I have added or updated unit tests that prove my fix is effective or that my feature works, and achieves sufficient code coverage. New and existing unit tests pass locally and in the build (below) with my changes
• [x] My changes generate no new warnings and running code analysis does not produce any issues
• [x] I have added or run the performance tests that depict optimal execution times
• [x] I have made corresponding changes to the documentation

[LeeDongGeon1996]

It's gone to v2..😵.. do we need to reset commit to ae966438b1a3c7091637470c89393b6054910597?

[DaveSkender]

It's gone to v2..😵.. do we need to reset commit to ae96643?

No, you probably added the semver tag on an individual commit, when it should really go in the commit message when you merge this PR, which is still registering at 0.9.x. I think it'll be fine when we merge with that tag again, since it will Squash that prior commit. Worst case is we fix the tags.

update: actually, looks like you did it right, see next note

[DaveSkender]

I’d recommend:

1. cancelling this PR and branch
2. doing one last PR to replace URLs (find/replace x 2)
3. after merge, add tag, then do manual build trigger on that tagged commit. release it. this release may throw a warning when it tries to retag, but that’s ok. I may need to do this tag as it may require directly adding it to main

[LeeDongGeon1996]

IMO, we can keep original url in docs. Because the original url(https://daveskender.github.io/Stock.Indicators.Python) is permanent for us, while the new one(https://python.stockindicators.dev/) is also for us but can be changed in the future whatever the reason is. Anyway access to the original will be redirected to the new one. How do you think about it?

[DaveSkender]

IMO, we can keep original url in docs. Because the original url(https://daveskender.github.io/Stock.Indicators.Python) is permanent for us, while the new one(https://python.stockindicators.dev/) is also for us but can be changed in the future whatever the reason is. Anyway access to the original will be redirected to the new one. How do you think about it?

Yah, that's a fair point. If I get hit by a bus and can't pay the domain fees, it could be a problem in the future; whereas the GitHub Pages URL should persist forever-ish. On the other hand, it might be confusing to be redirected too. Okay to keep, we can always revisit later.

[LeeDongGeon1996]

Yeah, just just just in case haha

[LeeDongGeon1996]

@DaveSkender (just for sharing my thought) I think it's better to use the new url to where the url is exposed in "form of URL", and use the original one to where the url is used for the link(such as inside <a>tag in html)