I see no mention of your resource adapter in the log file at all, that makes me believe that you are not starting your application using
standalone.sh -c standalone-teiid.xml
But at the same time, whatever the profile you started with, does have the Teiid subsystem in it, thus you were able to deploy the VDB etc. Check that. If that is not true, then provide your rar file, I will run locally and see if there is anything else is wrong.
If you are saying OrientDB has JDBC driver, then there are plenty of guides on how to configure a data source. For example, see this for Oracle . You want to use resource-adapter (RAR) when there is no JDBC driver and need another custom way to provide a manageable connection in WildFly.
I quickly looked at your RAR file, it does not follow the standard structure that is required by JEE to be a resource-adapter . That is the reason the WildFly server did not load your .rar file. If you are building a resource-adapter there are many examples in Teiid such as  to follow along.
Using the JDBC driver if OrientDB has one is the easiest way to configure. If not there is some coding required on your part to build a resource-adapter. Luckily Teiid provides all the basic libraries, templates to implement one.
I tried to install orientdb jdbc driver as module at first, but i failed.Module was failing to load at startup without any informative error logs.
So i occasionally found resource adapter installation guide and tried this one.
I will try to install jdbc driver once more.
The JDBC driver needs to support JDBC 4 compatible service loading mechanism. See this how to convert it if it already does not support service loading . You can open the JAR and quickly check if there is a "services" directory underneath "META-INF" directory or not. If not follow the directions in below article to make it compatible.