For #25799 - Fixes updating a framework located in an include file.

Previously, updates would fail for a framework if it wasn't explicitly referenced in the same environment file as the app/engine that uses it or if it wasn't included via the @ syntax.  

If it was in the same location but there was another instance defined in an include file then this was actually worse as it would be updated but the one that actually gets used at run-time (the one in the included file) wouldn't be!

This change fixes this so that the version used at run-time is always updated regardless of where it is defined.