[NFT Metadata Crawler] Add column to mark URIs to not be parsed

[just-in-chang]

Description

Many submitted tokens do not have proper JSON or image NFT metadata URIs. This column flags that so that they are not reprocessed and lets us have more accurate metrics regarding the success rate of the parser.

Test Plan

Tested locally + existing unit tests

[trunk-io]

⏱️ 3h 46m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
rust-unit-tests	45m	⬜ 🟩
windows-build	37m	🟩 🟩
rust-smoke-tests	29m	🟩
forge-e2e-test / forge	20m	🟩
execution-performance / single-node-performance	17m	🟩
forge-compat-test / forge	16m	🟩
rust-lints	16m	🟩 🟩
rust-images / rust-all	11m	🟩
run-tests-main-branch	8m	🟩 🟩
check	8m	🟩 🟩
cli-e2e-tests / run-cli-tests	7m	🟩
general-lints	5m	🟩 🟩
check-dynamic-deps	3m	🟩 🟩
node-api-compatibility-tests / node-api-compatibility-tests	53s	🟩
semgrep/ci	38s	🟩 🟩
file_change_determinator	22s	🟩 🟩
file_change_determinator	17s	🟩 🟩
file_change_determinator	11s	🟩
execution-performance / file_change_determinator	11s	🟩
permission-check	11s	🟩 🟩
permission-check	6s	🟩 🟩
permission-check	6s	🟩 🟩
permission-check	6s	🟩 🟩
determine-docker-build-metadata	3s	🟩
permission-check	2s	🟩

🚨 1 job on the last run was significantly faster/slower than expected

Job	Duration	vs 7d avg	Delta
forge-e2e-test / forge	20m	15m

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[github-actions]

✅ Forge suite compat success on aptos-node-v1.8.3 ==> 5d1ade568a077e9a6df53b55ef7a4f7b9fdeb78d

Compatibility test results for aptos-node-v1.8.3 ==> 5d1ade568a077e9a6df53b55ef7a4f7b9fdeb78d (PR)
1. Check liveness of validators at old version: aptos-node-v1.8.3
compatibility::simple-validator-upgrade::liveness-check : committed: 2710 txn/s, latency: 6985 ms, (p50: 6000 ms, p90: 7900 ms, p99: 23500 ms), latency samples: 181580
2. Upgrading first Validator to new version: 5d1ade568a077e9a6df53b55ef7a4f7b9fdeb78d
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1793 txn/s, latency: 16438 ms, (p50: 18600 ms, p90: 22900 ms, p99: 23200 ms), latency samples: 91480
3. Upgrading rest of first batch to new version: 5d1ade568a077e9a6df53b55ef7a4f7b9fdeb78d
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1836 txn/s, latency: 15935 ms, (p50: 18900 ms, p90: 22200 ms, p99: 22300 ms), latency samples: 93640
4. upgrading second batch to new version: 5d1ade568a077e9a6df53b55ef7a4f7b9fdeb78d
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3646 txn/s, latency: 8807 ms, (p50: 9900 ms, p90: 12000 ms, p99: 12600 ms), latency samples: 142220
5. check swarm health
Compatibility test for aptos-node-v1.8.3 ==> 5d1ade568a077e9a6df53b55ef7a4f7b9fdeb78d passed
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking

[github-actions]

✅ Forge suite realistic_env_max_load success on 5d1ade568a077e9a6df53b55ef7a4f7b9fdeb78d

two traffics test: inner traffic : committed: 6008 txn/s, latency: 6332 ms, (p50: 5700 ms, p90: 8800 ms, p99: 16300 ms), latency samples: 2613600
two traffics test : committed: 100 txn/s, latency: 2763 ms, (p50: 2300 ms, p90: 3000 ms, p99: 14500 ms), latency samples: 1880
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.221, avg: 0.197", "QsPosToProposal: max: 0.178, avg: 0.169", "ConsensusProposalToOrdered: max: 0.630, avg: 0.615", "ConsensusOrderedToCommit: max: 0.557, avg: 0.508", "ConsensusProposalToCommit: max: 1.171, avg: 1.123"]
Max round gap was 1 [limit 4] at version 662201. Max no progress secs was 8.614764 [limit 15] at version 2578036.
Test Ok

• Grafana dashboard
• Humio Logs
• Axiom Logs
• Test runner output
• Test run is land-blocking

[bowenyang007]

Add if exists and if not exists to make sure that the migration doesn't fail.