feat: Update scrollToBottom and scrollToTop methods to allow smooth behaviour

[quietdreamr]

Uses the scrollTo() method instead of directly setting the scrollTop. By default, it will still scroll instantly. When passing smooth = true, it'll set the behaviour to smooth.

[OvidijusParsiunas]

Hey @quietdreamr.
Thankyou for your contribution. I am currently quite busy, but before I can merge this I need to test it with other behaviours such as - streaming, media images with eventual loading and other UX aspects.
Apologies for not being able complete this right away as I have just moved countries and don't have much free time.

[quietdreamr]

Hey @quietdreamr. Thankyou for your contribution. I am currently quite busy, but before I can merge this I need to test it with other behaviours such as - streaming, media images with eventual loading and other UX aspects. Apologies for not being able complete this right away as I have just moved countries and don't have much free time.

No problem at all. It is not urgent. All the best with the moving process!

[OvidijusParsiunas]

Hey, I just had a look at your code and whilst it is great, there are a few things to note:

• Whilst you have made a great start, there is work to be done on actually allowing the devs to toggle whether the scrolling behaviour should be smooth or instant. This will involve the establishment of a toggle property/attribute that is not intrusive to the existing Deep Chat's API and at the same time would pave way for implementing new scroll related features in the future. This takes time to get right, hence needs to be carefully thought out. Additionally, there will ofcourse need to be work to update the Deep Chat's code to facilitate this and the documentation as well.
• The smooth scrolling seems to break the stream UX in the FireFox browser as the chat stops scrolling to the bottom. I wonder if anything can be done to fix this.

[OvidijusParsiunas]

Given the work mentioned above and outstanding issues that I still need to get through, I will keep the PR open but not merge it until I am comfortable with preparing it for a new release.

(I know that the code does not affect the existing functionality, but because not all of its branches can be activated - I do not want to confuse any other devs that may be using/analysing this project's code).

Thankyou for your great initiative once again!