[Bug]: Garbage observed during tiled composition on EHL with non-4 pixels output x coordinate

### Which component impacted?

Video Processing

### Is it regression? Good in old configuration?

No, this issue exist a long time

### What happened?

Sample_multi_transcode with below par file including tiled composition and non-4 pixel aligned x coordinate on EHL J6412. unexpected 2xheight green garbage rectangle observed on the first 15/16 x coordinate of this input stream. Meanwhile the output can strat from the configured x coordinate if it's non-4 pixels aligned.

no such issue on TGL-U with the same configuation. also no issue with normal composition without tile.

-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 3 -vpp_comp_dst_y 0 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 0
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 480 -vpp_comp_dst_y 0 -vpp_comp_dst_w 320 -vpp_comp_dst_h 240 -ext_allocator -fps 30 -vpp_comp_tile_id 0
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 960 -vpp_comp_dst_y 0 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 0
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 1440 -vpp_comp_dst_y 0 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 0

-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 0 -vpp_comp_dst_y 270 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 1
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 480 -vpp_comp_dst_y 270 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 1
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 961 -vpp_comp_dst_y 270 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 1
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 1440 -vpp_comp_dst_y 270 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 1

-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 3 -vpp_comp_dst_y 540 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 2
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 481 -vpp_comp_dst_y 540 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 2
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 962 -vpp_comp_dst_y 540 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 2
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 1440 -vpp_comp_dst_y 540 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 2

-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 0 -vpp_comp_dst_y 810 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 3
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 483 -vpp_comp_dst_y 810 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 3
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 963 -vpp_comp_dst_y 810 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 3
-i::h264 ./video/1080p.h264 -join -hw -async 4 -o::sink -vpp_comp_dst_x 1440 -vpp_comp_dst_y 810 -vpp_comp_dst_w 400 -vpp_comp_dst_h 270 -ext_allocator -fps 30 -vpp_comp_tile_id 3

-vpp_comp_only 16 -w 1920 -h 1080 -vpp_comp_num_tiles 4 -n 5 -async 4 -threads 2 -join -hw -i::source -ext_allocator -vpp::vid -fps 30 -ec::nv12 -vpp_comp_dump output.yuv

media-driver: 22.6.4
libva: 2.14.0
media sdk: 21.3


### What's the usage scenario when you are seeing the problem?

Others

### What impacted?

Can't use non-4 pixels aligned x coordinate which is required in real use case.

### Debug Information

no such issue on TGL-U with the same configuation. also no issue with normal composition without tile.

root@test-US-M5420:/home/test/james/concurrent-video-analytic-pipeline-optimization-sample-l# vainfo
error: XDG_RUNTIME_DIR not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.14.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /opt/intel/svet/msdk/lib/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.14.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.6.4 (7b818166d)
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
VAProfileNone : VAEntrypointStats
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSliceLP
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSliceLP
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointEncPicture
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
VAProfileVP8Version0_3 : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSliceLP
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSliceLP
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile1 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileVP9Profile3 : VAEntrypointVLD
VAProfileHEVCMain422_10 : VAEntrypointVLD
VAProfileHEVCMain444 : VAEntrypointVLD
VAProfileHEVCMain444 : VAEntrypointEncSliceLP
VAProfileHEVCMain444_10 : VAEntrypointVLD
VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP

### Do you want to contribute a patch to fix the issue?

No.