Fixes force-uuid behavior

Prior to this change and due to an error in the recent removal of asec
code from the framework, force-uuid installs were treated the same as
any non-internal install, relying on resolve and install preferences
instead of explicitly using the forced uuid. This change corrects that
behavior.

Bug: 109941548
Test: atest CtsAppSecurityHostTestCases
Change-Id: Id2dddfbb78a5083e74ef4ae1f8df8f468f724546