format() emits `CREATE OR REPLACE ROW POLICY`, which ClickHouse rejects

`format()` re-prints a parsed `CREATE ROW POLICY OR REPLACE policy_name ...` statement as `CREATE OR REPLACE ROW POLICY policy_name ...`, which the ClickHouse server rejects — the documented syntax only allows `OR REPLACE` after `POLICY`, never after `CREATE`.

## Reproduction

```js
const { parse, format } = require('@clickhouse/parser');

const sql = 'CREATE ROW POLICY OR REPLACE p ON db.table USING db.table.tenant_id = 1';

parse(sql)[0].or_replace; // true — parses correctly

format(parse(sql));
// => CREATE OR REPLACE ROW POLICY p ON db.table USING db.table.tenant_id = 1;
// invalid: https://clickhouse.com/docs/reference/statements/create/row-policy
// only accepts CREATE [ROW] POLICY [IF NOT EXISTS | OR REPLACE] policy_name ...
```

The parser also accepts that same invalid form as input, without error:

```js
const bad = 'CREATE OR REPLACE ROW POLICY p ON db.table USING db.table.tenant_id = 1';

parse(bad)[0].or_replace; // true — accepted, though the server would reject this syntax
```

## Suggested fixes

1. Fix parser to accept `OR REPLACE` in correct position.
2. Fix `format()` to emit `OR REPLACE` in the correct position.

## Environment

`@clickhouse/parser` 0.3.0

Start with the parse() and format() entry points in @clickhouse/parser and reproduce the CREATE ROW POLICY OR REPLACE example from the issue. Trace how or_replace is parsed and emitted; done means valid ClickHouse syntax is formatted correctly and the invalid CREATE OR REPLACE form is no longer accepted.

Written by the indexing model from the issue text.