Converted ads keep showing

[btlechowski]

Found while testing #6536.

The ads conversion is linked to creativeSetId. There could be many ads under one creativeSetId.
Any ad can convert the set, which is expected.
Not expected is that we keep showing ads from the set that was converted. Our clients may not like that because it is unnecessary cost.
According to @jsecretan this is expected behavior at this stage, but something we should definitely address in the future.

Steps to Reproduce

1. Create a catalog with multiple ads under one creativeSetId
2. Show the ad
3. Convert the ad
4. Trigger more ads from the set

Note: reproduced on staging

Actual result:

Ads keep showing for converted set

Expected result:

Ads are not showing

Reproduces how often:

100% repro rate

Brave version (brave://version info)

Brave	1.7.54 Chromium: 80.0.3987.132 (Official Build) nightly (64-bit)
Revision	fcea73228632975e052eb90fcf6cd1752d3b42b4-refs/branch-heads/3987@{#974}
OS	Ubuntu 18.04 LTS

Brave	1.7.54 Chromium: 80.0.3987.132 (Official Build) nightly (64-bit)
Revision	fcea73228632975e052eb90fcf6cd1752d3b42b4-refs/branch-heads/3987@{#974}
OS	Windows 7 Service Pack 1 (Build 7601.24544)

cc @brave/legacy_qa @tmancey @jsecretan @rebron @davidtemkin

[btlechowski]

Verification passed on

Brave	1.8.82 Chromium: 81.0.4044.113 (Official Build) dev (64-bit)
Revision	e3225dafb0475864a1812a374d73a92e391635ac-refs/branch-heads/4044@{#936}
OS	Ubuntu 18.04 LTS

Staging catalog used: 8645.txt
The issue still reproduces. Per our process I logged a new issue: #9436

Verified using

Brave	1.8.82 Chromium: 81.0.4044.113 (Official Build) dev (64-bit)
Revision	e3225dafb0475864a1812a374d73a92e391635ac-refs/branch-heads/4044@{#936}
OS	macOS Version 10.14.6 (Build 18G3020)

As noted above, issue still reproduces. Commented on #9436.

Verification passed on

Brave	1.8.84 Chromium: 81.0.4044.122 (Official Build) (64-bit)
Revision	44f4233f08910d83b146130c1938256a2e05b136-refs/branch-heads/4044@{#963}
OS	Windows 10 OS Version 1803 (Build 17134.1006)

As noted above, issue still reproduces. Commented on #9436.