(you don't have to strictly follow this form)

**Describe the bug**
When using `ORDER BY column_name COLLATE 'en'`, `COLLATE` is ignored if `column_name` is the primary key
 
**How to reproduce**
* version 21.1.2
* `CREATE TABLE` statements for all tables involved:
```
CREATE TABLE test.test_collation
(
    `v` String,
    `v2` String
)
ENGINE = MergeTree
ORDER BY v
SETTINGS index_granularity = 8192
```
* Sample data:
```
insert into test.test_collation values ('A', 'A')
insert into test.test_collation values ('B', 'B')
insert into test.test_collation values ('C', 'C')
insert into test.test_collation values ('a', 'a')
insert into test.test_collation values ('b', 'b')
insert into test.test_collation values ('c', 'c')
```
* Queries to run that lead to unexpected result
Primary key
```
SELECT *
FROM test.test_collation
ORDER BY v ASC COLLATE 'en'

Query id: fa84ae7a-abe7-4886-99cd-eba7ad5d5fc4

┌─v─┬─v2─┐
│ A │ A  │
│ B │ B  │
│ C │ C  │
│ a │ a  │
│ b │ b  │
│ c │ c  │
└───┴────┘
```
Separate column
```
SELECT *
FROM test.test_collation
ORDER BY v2 ASC COLLATE 'en'

Query id: 04401f85-3cb2-442c-8c89-e3328d1615cd

┌─v─┬─v2─┐
│ a │ a  │
│ A │ A  │
│ b │ b  │
│ B │ B  │
│ c │ c  │
│ C │ C  │
└───┴────┘
```

**Expected behavior**
Both of these queries to return the rows in the same order

* returned by getColumnName is not enough, and we have to use the
             * column id set by EA. In principle, this logic applies to all kinds
             * of columns, not only literals. Literals are especially problematic
             * for two reasons:
             * 1) confusing different literal columns leads to weird side
             *    effects (see 01101_literal_columns_clash);
             * 2) the disambiguation mechanism in SyntaxAnalyzer, that, among
             *    other things, creates unique aliases for columns with same
             *    names from different tables, is applied before these temporary
             *    columns are created by ExpressionAnalyzer.
             * Similar problems should also manifest for function columns, which
             * are likewise created at a later stage by EA.
             * In general, we need to have explicit separation between display
             * names and identifiers for columns. This code is a workaround for
             * a particular subclass of problems, and not a proper solution.
             */
            if (const auto * as_literal = ast->as<ASTLiteral>())
            {
                source_name = as_literal->unique_column_name;
                assert(!source_name.empty());
            }
            result_columns.emplace_back(source_name, result_name);
            step.addRequiredOutput(result_columns.back().second);
        }
    }
    auto actions = chain.getLastActions();
    actions->project(result_columns);
    return actions;
}
void ExpressionAnalyzer::appendExpression(ExpressionActionsChain & chain, const ASTPtr & expr, bool only_types)