text: Title: Unique items should be allowed as list in Pydantic v2
  Body: **Describe the bug**
  When Pydantic v2 is used, i.e., `--output-model-type pydantic_v2.BaseModel`, any field tagged with unique items will always be created as set. Where it is understandable to use set to ensure unique items, there is a distinct difference between set and list. Some important ones are:
  * Set does not preserve order like list. 
  * Set requires item hashable.
  
  As such, it is desirable to use list to store data even when unique items are used for many applications.
  
  Noted that there is a `--use-unique-items-as-set` flag, which usually means by default the list is used (It is the case when other output model types are used.) May I suggest to use list for Pydantic v2 as well? Alternatively, can we support a `--use-unique-items-as-list` flag?
  
  **To Reproduce**
  
  Example schema:
  ```json
  {
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "title": "Example",
    "type": "object",
    "properties": {
      "data": {
        "type": "array",
        "uniqueItems": true
      }
    }
  }
  ```
  
  Used commandline:
  ```
  $ datamodel-codegen --output-model-type pydantic_v2.BaseModel --input schema.json --output model.py
  ```
  
  **Expected behavior**
  Ability to use list instead of set in the output model.
  
  **Version:**
   - OS: macOS
   - Python version: 3.11.4
   - datamodel-code-generator version: 0.21.2
  
  