feat: Add --ignore-version option to mason add to bypass brick.yaml version checks

**Description**

Currently, when using `mason add` to install a brick, the command fails if the brick's `brick.yaml` includes a `mason` environment constraint that does not match the current mason version.

Example:

```
The current mason version is 0.1.1.
Because a_page requires mason version >=0.1.0-dev.26 <0.1.0, version solving failed.
```

This is a common issue for older bricks created before Mason 0.1.0 was released.

I propose adding an `--ignore-version` (or `--force`) flag to `mason add` that bypasses this version check and logs a warning instead, allowing the user to proceed.

---

**Requirements**

- [ ] Add `--ignore-version` (or `--force`) flag to `mason add`
- [ ] When this flag is used, skip the `mason` version constraint validation from `brick.yaml`
- [ ] Print a warning message indicating version incompatibility
- [ ] Keep current behavior strict by default

---

**Additional Context**

Many community bricks on GitHub are locked to old dev versions like `0.1.0-dev.47`, making them unusable on the current stable version (`0.1.1`).

This enhancement would let users install older bricks without modifying their `brick.yaml` manually.

Example usage:

```bash
mason add --global a_page --ignore-version
```