Conflicting language around type annotations in strict syntax documentation

[sersorrel]

The new documentation about strict syntax states that when you use def, you must not include a type annotation:

nextflow/docs/updating-syntax.md

Line 252 in 67ffc8a

In the strict syntax, variables must be declared with `def` and must not specify a type:

However, a later example includes a type annotation, and even states they they are preferred over as-casts:

nextflow/docs/updating-syntax.md

Lines 332 to 336 in 67ffc8a

	In the strict syntax, only hard casts are supported. However, hard casts are discouraged because they can cause unexpected behavior if used improperly. Groovy-style type annotations should be used instead:
	```groovy
	def Map map = readJson(json)
	```

There is a note that type annotations will be addressed properly in the future:

nextflow/docs/updating-syntax.md

Line 264 in 67ffc8a

Because type annotations are useful for providing type checking at runtime, the language server will not report errors for Groovy-style type annotations at this time. Type annotations will be addressed in a future version of the Nextflow language specification.

but this only mentions that the language server will not produce an error – should this instead say that Nextflow as a whole will accept type annotations at the moment? (but, for example, that they are discouraged and may cause an error in the future, if that is the case?)

[bentsherman]

This page used to be only about the language server, but now that the strict syntax is in Nextflow, yes it should talk about Nextflow in general and not just the language server

Both will accept Groovy-style type annotations for now. Once we add type annotations to the strict syntax, we'll start reporting warnings (and eventually errors) for the old way