Something not okay with enum types

Nobody has claimed this yet.

### How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

### Which OS are you using?

Linux

### What is the issue affecting?

Type Checking

### Expected Behaviour

```lua
---@enum EnumAB
local e = {
A = 0,
B = 1,
}

---@type EnumAB
local a = 1

---@type EnumAB.A
local ea = e.A

---@type EnumAB.B
local eb = e.B

---@type EnumAB.B
local eb = e.A -- Cannot assign `EnumAB.A` to `EnumAB.B`

---@type EnumAB
local ee = eb

---@type EnumAB.A
local eea = ee -- Cannot assign `EnumAB` to `EnumAB.A`
```

### Actual Behaviour

```lua
---@enum EnumAB
local e = {
A = 0,
B = 1,
}

---@type EnumAB
local a = 1

---@type EnumAB.A
local ea = e.A -- Cannot assign `integer` to `EnumAB.A`

---@type EnumAB.B
local eb = e.B -- Cannot assign `integer` to `EnumAB.B`

---@type EnumAB.B
local eb = e.A -- Cannot assign `EnumAB.A` to `EnumAB.B`

---@type EnumAB
local ee = eb -- Cannot assign `EnumAB.B` to `EnumAB`.

---@type EnumAB.A
local eea = ee -- Cannot assign `EnumAB` to `EnumAB.A`
```

### Reproduction steps

-

### Additional Notes

`EnumAB.A` is most likely an unintended side effect, but having restrictions inside the enum seems like a good idea

### Log File

_No response_

No source file, entry point, or test is named. Reproduce the enum assignments from the issue in the Lua language server's Visual Studio Code extension on Linux, then trace the type-checking behavior and define regression coverage for the expected relationships between EnumAB, EnumAB.A, and EnumAB.B.

Written by the indexing model from the issue text.