There are still quite a few places in ddl examples and documentation where we show a create vdb statement that has a version. This is no longer meaningful.

In core functionality (teiid and teiid-spring-boot) we may need to make language and other changes to fully realize better handling:

• For example vdb import statements should likely have an optional version - so that when creating a vdb via a mechanism that explicitly provides dependencies the version is not also needed in the ddl.
• The notion of appending a version could be dropped from connection handling (with all interfaces) in teiid spring boot
• A version is still in generated artifacts such as https://github.com/teiid/teiid-openshift-examples/blob/165d45fdf0ede38ac54a9776c07c56cfa88ff2d2/rdbms-example/vdb-as-maven-artifact/vdb-build/target/vdb.ddl which ideally could match the project version instead.