drivers: video: gc2145: fixes compatible prefix of gc2145

[uLipe]

This change is required to fix dts error of unknown vendor when parsing the compatible string when instancing gc2145.

Although it builds applications correctly, this error makes the ci to fail if some board instance this sensor on its dts, this is caused because it was not using the already existing prefix galaxycore, it was merged using gc prefix instead.

[kartben]

This looks wrong? Why wasn't the existing galaxycore vendor picked in the first place? The proper fix would be to update the binding/driver to use that instead of gc

[uLipe]

Oh, that is true, I will change this PR, I did not realize there is a prefix yet, thanks @kartben

[uLipe]

Hi Folks, can we merge this? I would like to have this one merged beefore the camera support from Nicla Vision (or other use case for GC2145) comes in.

Thank you :)

[nashif]

@uLipe Please do not self-assign PRs, the zephyr bot usually does that, you should only be assigned if you are the maintainer of the area being changed.

[kartben]

Hi Folks, can we merge this? I would like to have this one merged beefore the camera support from Nicla Vision (or other use case for GC2145) comes in.

Thank you :)

It will get merged in the next merge batch. It hadn't been in review for 48 business hours until very recently, so that's why it hasn't been merged yet :)

[uLipe]

@uLipe Please do not self-assign PRs, the zephyr bot usually does that, you should only be assigned if you are the maintainer of the area being changed.

Thank you for pointing @nashif I was getting the wrong understanding of what assign PR means, it is clear now.