[TRANSFORMATIONS | GPU] Add a Validate pass after MoveEltwiseUpThroug…

…hDataMovScalar for element type resolution (openvinotoolkit#27464)

[TRANSFORMATIONS | GPU] Add a Validate pass after
MoveEltwiseUpThroughDataMovScalar

After executing the MoveEltwiseUpThroughDataMovScalar transforamtion
some node's element types may appear to be in inconsistent/corrupted
state. Fix it by inserting a Validate pass after the transformation for
resolving the node's element types.

This commit is a workaround until the 141764 is fixed which resolves the
issue of Validate passes.

Ticket:
* CVS-151111

Signed-off-by: Andrii Staikov <andrii.staikov@intel.com>

Signed-off-by: Andrii Staikov <andrii.staikov@intel.com>

src/plugins/intel_gpu/src/plugin/transformations_pipeline.cpp

@@ -824,6 +824,11 @@ void TransformationsPipeline::apply(std::shared_ptr<ov::Model> func) {
             ov::op::v3::Broadcast::get_type_info_static(),
         };
         manager.register_pass<ov::pass::MoveEltwiseUpThroughDataMovScalar>(allowed_data_movement_ops);
+        // FIXME (151111): this Validate is added as a workaround for resolving element
+        // types after MoveEltwiseUpThroughDataMovScalar. It has to be removed
+        // after 141764 is fixed as there's a clear issue with Validate passes
+        // not working properly.
+        manager.register_pass<ov::pass::Validate>();
 
         manager.register_pass<ov::intel_gpu::ClampFP16Output>();
         manager.register_pass<ov::intel_gpu::ConvertMatMulToFullyConnected>();