reportOptionalMemberAccess after raise ValueError

Nobody has claimed this yet.

**Describe the bug**
After checking variable for none value with valueerror raise pylance says about possible none value

**Code or Screenshots**
```python
# Tag is html tag of bs4
# a is value Optional[Tag] (Tag | None)
if a is None:
raise ValueError("...")
b = a.text # here error, pylance says that .text is not attr of None
```

**VS Code extension or command-line**
vscode; pylance 2025.16.0

Start with the provided minimal Python example in the Pylance VS Code extension and reproduce the diagnostic with pylance 2025.16.0. Investigate how the checker handles narrowing after raising ValueError; done means the diagnostic is no longer reported for a.text after the None check, with regression coverage for this example.

Written by the indexing model from the issue text.