store: ensure consistent id type in FindRangeQuery SQL output

[shiyasmohd]

When using subgraph composition and indexing entity of different type id, the subgraph wouldn't sync due to the below error

UNION types bytea and text cannot be matched

This was because the FindRangeQuery SQL generator wasn't casting entity IDs to a consistent type, causing UNION ALL operations to fail when merging results from subgraphs with different ID types

[shiyasmohd]

@incrypto32 Changes:

• Added unit test in query_tests.rs
• Covered different entity id for source subgraph case in integration tests