Request: Support `@field` in both enum and table definitions.

Request: Allow adding a field type to tables and enum definitions using the @field annotation.

This is useful for generating meta files from C code where there is no Lua table literal to copy.

See current behaviour below:

@class

✅ Using @field

---@class Foo
---@field myField 5
Foo = {}

✅ Using literal code

---@class Foo
Foo = {
  myField = 5,
}

✅ Using type annotation

---@class Foo
Foo = {
  ---@type 5
  myField = nil,
}

@enum

❌ Using field

---@enum Foo
---@field myField 5
Foo = {}

Error: The field must be defined after the class.Lua Diagnostics.(doc-field-no-class)

✅ Using literal code

---@enum Foo
Foo = {
  myField = 5,
}

✅ Using type annotation

---@enum Foo
Foo = {
  ---@type 5
  myField = nil,
}

Untyped table

❌ Using field

---@field myField 5
Foo = {}

Error: The field must be defined after the class.Lua Diagnostics.(doc-field-no-class)

✅ Using literal code

Foo = {
  myField = 5,
}

✅ Using type annotation

Foo = {
  ---@type 5
  myField = nil,
}

Commencez par suivre le traitement de @field associé au diagnostic doc-field-no-class ; l'issue fournit des exemples Lua pour @class, @enum et les tables non typées. C'est terminé lorsque les définitions de @field fonctionnent pour des définitions d'enum et de table comme dans les exemples sans ce diagnostic, tout en conservant la prise en charge du comportement existant des classes.