feat(license): add `LICENSE` file with `MIT`

# feat(license): add `LICENSE` file with `MIT`

| ⏱️ Estimate | 📊 Priority | 📏 Size | 📅 Start | 📅 End |
| --- | --- | --- | --- | --- |
| 2h | P2 | S | 02-03-2026 | 02-03-2026 |

## 📸 Screenshots

| Current | Expected |
| :---: | :---: |
| N/A — This change has no visual impact. | |

## 📝 Summary

- Create `LICENSE` file with `MIT` license text
- Add `license` field with value `MIT` to `package.json`
- Document the license type in the `README.md` file

## 💡 Why this change?

- Open source projects should include a `LICENSE` file to define the terms of use
- The `MIT` license is permissive and widely used for open source projects

## ✅ Benefits

- Legal clarity for code usage and distribution
- Encourages open source collaboration
- Standard practice for public repositories
- Protects contributors and users

## 📋 Steps

### Phase 1: Create `LICENSE` file
- [x] Create `LICENSE` file in repository root with `MIT` License text:

```text
MIT License

Copyright (c) 2026 Beatriz Sopeña Merino

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
```

### Phase 2: Update `package.json`
- [x] Add `license` field to `package.json`:

```bash
npm pkg set license="MIT"
```

```diff
{
"name": "angular-setup",
"version": "0.0.0",
+ "license": "MIT",
...
}
```

### Phase 3: Add `License` section to `README.md`
- [x] Add `License` section at the end of `README.md`:

```markdown
## 📄 License

This project is licensed under the `MIT` License, which allows free use, modification and distribution. See [LICENSE](LICENSE) for details.
```

## 🧪 Tests

- [x] Verify `LICENSE` file exists in repository root
- [x] Verify `package.json` has `"license": "MIT"`
- [x] Verify `README.md` has `## 📄 License` section

## 📌 Notes

### License comparison
| Aspect | `MIT` | `ISC` | `UNLICENSED` |
| --- | --- | --- | --- |
| Type | Permissive | Permissive | All rights reserved |
| Length | ~170 words | ~70 words | N/A |
| `npm` default | No | Yes | No |
| GitHub option | Yes | No | No |
| Commercial use | Yes | Yes | No |
| Sublicensing | Explicitly allowed | Implicitly allowed | Not allowed |
| Recommendation | Preferred by `ISC` org | Simpler version of `MIT` | For private/client projects |

## 🔗 References

### Files to create
- `LICENSE`

### Files to modify
- `package.json`
- `README.md`

### Documentation
- https://choosealicense.com/licenses/mit/
- https://docs.npmjs.com/cli/v10/configuring-npm/package-json#license