Return an error when direct-nested-loading a subasset

[andriyDev]

Objective

• Previously, attempting to direct-nested-load a subasset would return the root of the nested-loaded asset. This is most problematic when doing direct-nested-untyped-loads of subassets, where you may not even realize you're dealing with the entirely wrong asset (at least with typed loads, most of the time the root asset has a different type from the subasset, and so at least you'd get an error that the types don't match).

Solution

• We now return an error when doing these kinds of loads.

Note an alternative would be to "solve" this problem, by just looking up the appropriate subasset after doing the nested load. However there's two problems: 1) we don't know which subassets of the root asset are necessary for the subasset we are looking up (so any handles in that subasset may never get registered), 2) a solution will likely hamper attempts to resolve #18010. AFAICT, no one has complained about this issue, so it doesn't seem critical to fix this for now.

Testing

• Added a test to ensure this returns an error. I also checked that the other before this was just a mismatched type error, meaning it was trying to pass off the root asset type CoolText as the subasset type SubText (which would have worked had I not been using typed loads).

[alice-i-cecile]

I really like pushing asset loading towards clear, error-returning behavior. It's way too hard to reason about anything else IMO.

[andriyDev]

(forgot to rebase before pushing, sorry)