Fix Order By for composite property projection in Criteria

[bahusoid]

Fixes #1103

[hazzik]

I have another fix in mind. I tried to implement it a while back. The idea is to get rid of StringHelper.RemoveAsAliasesFromSql and instead generate projections without aliases when needed.

[bahusoid]

@hazzik Original logic calls GetColumnAliasesUsingProjection for properties where StringHelper.RemoveAsAliasesFromSql is not involved.
So my fix uses GetColumnAliasesUsingProjection for both properties and properties projections (along with Id projection).
StringHelper.RemoveAsAliasesFromSql is called otherwise and I refactored this place to use CriterionUtil.GetColumnNamesUsingProjection. So your suggested fix is unrelated to this PR (but yes it might be useful in other scenarios with composite properties )

[bahusoid]

This change is actually unrelated to OrderBy fix. But it fixes cases when GetColumnNamesUsingProjection is called for composite property projections (in tests it's covered by .Where(Restrictions.Eq(Projections.Id(), id)))