Version string mismatch in pyproject.toml / master branch still shows 0.14.1

### Custom Node Testing

- [x] I have tried disabling custom nodes and the issue persists (see [how to disable custom nodes](https://docs.comfy.org/troubleshooting/custom-node-issues#step-1%3A-test-with-all-custom-nodes-disabled) if you need help)

### Expected Behavior

Description:
The master branch is currently reporting as version 0.14.1 even though v0.14.2 has been tagged and released.

Proof:

pyproject.toml on master currently lists version = "0.14.1".

My local install at commit 04a55d50 (which is post-v0.14.2) still initializes as 0.14.1.

This causes confusion for users running the update scripts who believe their update failed because the console output doesn't reflect the new version.

Suggested Fix:
Bump the version string in pyproject.toml to 0.14.2 (or 0.14.3-pre) on the master branch.

### Actual Behavior

The console continues to display ComfyUI version: 0.14.1. Even though the code includes recent commits (like 04a55d50), the pyproject.toml and comfyui_version.py files still have the hardcoded string 0.14.1. This causes significant user confusion, leading people to believe their update scripts or git pull commands have failed.

### Steps to Reproduce

Perform a git pull on the master branch or run update_comfyui.bat.

Verify via git status or git rev-parse HEAD that the local commit is current (e.g., commit 04a55d50).

Launch ComfyUI.

Observe that the terminal output still identifies the version as 0.14.1.

Check pyproject.toml in the root directory and see version = "0.14.1".

### Debug Logs

```powershell
-
```

### Other

pyproject.toml lists version = "0.14.1"

comfyui_version.py is still at __version__ = "0.14.1"