docs: Update docs for v0.8.1

[LeeDongGeon1996]

Description

• Update docs for import path.
• Updates for v0.8.1

Fixes #244

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]

Because from stock_indicators.indicators.common.enums import PivotPointType is shortened to from stock_indicators import PivotPointType in the docs, 4f9e2155b7faaaeeedd615f5dc01af08a743bbec has to be cherrypicked to the new branch from tag 0.8.0, and it's going to be released as 0.8.1 with patch-version up.

@DaveSkender I think I need a new branch from tag 0.8.0. Could you make it as a protected branch with named 0.8?

[DaveSkender]

I think I need a new branch from tag 0.8.0. Could you make it as a protected branch with named 0.8?

I’m not sure I follow this logic. Is this a rebase issue, or something we can just fix in a second commit (before releasing)?

[LeeDongGeon1996]

I'd like to include only  4f9e215 in v0.8.1 (because it's related UX). But we are merging every PR to main till now. So there's no way to exclude some un-released commits before  4f9e215 . That's why I need a new branch to make a backport.

[DaveSkender]

I've created a branch v0.8 from that tag.