Automation should prefer first future inValue instead of nothing

### Enhancement Summary

Currently automation controls parameters during and after automation patterns, which basically means the entire track after the first pattern.

However before the first pattern the value can be anything random, which is especially janky when you stop playback in the middle of a track and moving into the beginning, causing unexpected results.

From a practical standpoint this means a lot of unnecessary "set to value" automation patterns near track beginning, or even more cursed, one-off global automation.

Considering automation is usually smooth (and those that aren't can use outvalues to account for sudden jumps), it makes sense to set the initial value to first occurring inValue of the automation track.

### Implementation Details / Mockup

uuuhh just use the first dot of the automation on a particular parameter

### Please search the issue tracker for existing feature requests before submitting your own.

- [x] I have searched all existing issues and confirmed that this is not a duplicate.

Start by tracing the automation-track logic for parameter values before and during automation patterns. Confirm how the first inValue is identified and how playback behaves when entering a track before its first pattern. Done means the initial value comes from that first inValue instead of an unrelated or random value, without requiring extra beginning-of-track automation.

Written by the indexing model from the issue text.