Proposal: VB remove limitations for using using keywords as names

```
Public Class C1
Public Property select As Integer
End Class
```

Compiler show error because name of property is keyword. This is very stretched limitation, without any good reasons. These limitations should be removed.

The issue provides only a Visual Basic example using `select` as a property name and does not mention compiler files, tests, or entry points. Start by reviewing how the compiler classifies keywords in declarations, then determine the affected naming rules and the tests needed to define which keyword usages should be accepted.

Written by the indexing model from the issue text.