Added more literal type resolution logic to claimLiteral

If the Class of the value doesn't tell which layer0-builtin type
resource to use, try to use the Datatype provided by the binding to
resolve the builtin type resource. If that fails also, resort to the the
old fallback behavior.

gitlab #496

Change-Id: Ie55984d2812bafa84c12f0a776b0d6de7e6a905d
(cherry picked from commit d788b5fea66a6dffe1649de57bc83705e6027bc0)