feat(tracking): tag OpenCart address lookups + differentiate AddressFinder/PostcodeLookup

[devin-ai-integration]

Summary

Adds Ideal Postcodes usage-tracking tags to OpenCart, matching the pattern already applied to magento (#583), bigcommerce (#635), shopwired (#627), and woocommerce (#928).

Tags emitted on the wire:

• AddressFinder → tags=opencart,addressfinder
• PostcodeLookup → tags=opencart,postcodelookup

Each widget stays on its correct delivery mechanism — AddressFinder bypasses core-interface's appendTags, so it must receive tags via queryOptions/resolveOptions; PostcodeLookup forwards a top-level tags[] through client.config.tags:

const tags = ["opencart"];
const postcodeLookupTags = [...tags, "postcodelookup"];          // PL: top-level tags[]
const addressFinderTags = [...tags, "addressfinder"].join(","); // AF: query/resolve options

AddressFinder.watch({ queryOptions: { tags: addressFinderTags }, resolveOptions: { tags: addressFinderTags }, ... });
watch({ ..., tags: postcodeLookupTags });  // setupPostcodeLookup & setupShippingPostcodeLookup

Regenerated opencart.js (minified frontend bundle). Within Taggable limits (≤5 tags, ≤16 chars each).

Link to Devin session: https://app.devin.ai/sessions/061cf09b00a5439fb1f42842bc62b1a8
Requested by: @mfilip

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring