Fix for accessory dynamic bones causing a faulty baseline to be collected.

[krypto5863]

Fix for #58

I tried to keep things as simple as possible, when the baseline is first collected, we simply disable the component, which causes the bones to assume their resting position, collect the baseline, and set things back to how they were.

[ManlyMarco]

I think the new DB-related members should not be public unless there's already a plan to use them in another plugin.

Can there only ever be one DB affecting a bone? What if there's a DB inside another DB and you return the inner one because it's first in the list?

[krypto5863]

I don't believe it should ever be the case that multiple DBs affect a bone or a string of bones, even if they're later on down the line. I think that'd be a bug tbh.

Nah pub prop is just an oversight, I'll make it internal.