[EPIC] Refactor Doris IT container

### Describe the proposal

We use an all-in-one Docker image as the Doris IT container, which is convenient to use. However, I found some shortcomings.

- It has only one Backend (BE), so creating a table with default properties will result in an error. see #3173
- In Doris 2.1.x, the Doris community advises utilizing docker-compose for initiating a Doris cluster. To support new features in Doris 2.1.x, it is also necessary to use docker-compose.

### Task list

- [ ] introduce docker-compose in `org.apache.gravitino.integration.test`
- [ ] update DorisContainer to use docker-compose
- [ ] remove code about `replication_num` #4343

Start by locating the org.apache.gravitino.integration.test module and the DorisContainer implementation. Review the existing all-in-one container setup and the task list, then determine how docker-compose should be introduced, how DorisContainer should use it, and where replication_num handling lives. Done means all three checklist items are completed and the Doris integration tests pass.

Written by the indexing model from the issue text.