26147 mari polish

- Addressed code review from previous pull request.
- Changed code that finds geo & geo version for a publish to use the id rather than the path.  This also now looks for matching publish versions by searching on entity, task, name, type instead of path as it was doing previously!
- Added version check and standard warning for untested Mari versions to engine init 
probably an unnecessary question but just in case: would there be value in doing some sort of batch approach here? What if there is a lot of geometries in the scene? Would it help to do a sg batch call in that case? Sorry if this is irrelevant, i don't really know mari well enough to have an informed opinion. :)