split KernelF languages plugin

[lhartl]

Currently, there is one plugin containing all KernelF languages. The plan is to split it up in at least 3 plugins: e.g. core, advanced and experimental

Current structure of the languages:

core:

• org.iets3.core.expr.base
• org.iets3.core.expr.collections
• org.iets3.core.expr.lambda
• org.iets3.core.expr.path
• org.iets3.core.expr.repl
• org.iets3.core.expr.simpleTypes
• org.iets3.core.expr.simpleTypes.tests
• org.iets3.core.expr.tests
• org.iets3.core.expr.toplevel
• org.iets3.core.expr.tracing

advanced

• org.iets3.core.expr.adt
• org.iets3.core.expr.data
• org.iets3.core.expr.dataflow
• org.iets3.core.expr.datetime
• org.iets3.core.expr.doc
• org.iets3.core.expr.lookup
• org.iets3.core.expr.math
• org.iets3.core.expr.messages
• org.iets3.core.expr.metafunction
• org.iets3.core.expr.natlang
• org.iets3.core.expr.query
• org.iets3.core.expr.temporal
• org.iets3.core.expr.typetags
• org.iets3.core.expr.typetags.lib
• org.iets3.core.expr.typetags.units
• org.iets3.core.expr.typetags.units.quantity
• org.iets3.core.expr.util

stateful

• org.iets3.core.expr.mutable
• org.iets3.core.expr.process
• org.iets3.core.expr.statemachines

Which languages could be moved to an experimental plugin?

• org.iets3.core.expr.adt
• org.iets3.core.expr.data
• org.iets3.core.expr.dataflow
• org.iets3.core.expr.lookup
• org.iets3.core.expr.natlang
• org.iets3.core.expr.repl

[wsafonov]

org.iets3.core.expr.data and org.iets3.core.expr.lookup should be better left in advanced (being already used in a customer project)