Consider module as function call for highlighting

Their semantic is closer to a function call (like i.e: Bazel rules)
rather than a module/namespace.

Similarly for their properties, which are more like parameters than
members.

queries/highlights.scm

@@ -42,11 +42,11 @@
 (identifier) @variable
 
 (module
-  type: (identifier) @module)
+  type: (identifier) @function.call)
 
 (module
   (property
-    field: (identifier) @variable.member))
+    field: (identifier) @variable.parameter))
 ; }}}
 
 ; Built-ins {{{

test/highlight/modules.bp

@@ -1,21 +1,21 @@
 foo {}
-// <- module
+// <- function.call
 
 foo ()
-// <- module
+// <- function.call
 
 foo {
-// <- module
+// <- function.call
     field: 12,
-    // <- variable.member
+    // <- variable.parameter
     another_field: 27,
-    // <- variable.member
+    // <- variable.parameter
 }
 
 foo (
-// <- module
+// <- function.call
     field = 42,
-    // <- variable.member
+    // <- variable.parameter
     done = false,
-    // <- variable.member
+    // <- variable.parameter
 )

test/highlight/properties.bp

@@ -1,6 +1,6 @@
 foo {
     field: {
-    // <- variable.member
+    // <- variable.parameter
         key: 42,
         // <- property
     },

test/highlight/select.bp

@@ -11,5 +11,5 @@ select = 42
 // Or module property
 foo {
     select: 42,
-    // <- variable.member
+    // <- variable.parameter
 }