libvpx: add encoder targets

[catenacyber]

and nalloc (alloc failures) targets

cc @jzern after merge of https://chromium-review.googlesource.com/c/webm/libvpx/+/7032244?usp=email and previous

[github-actions]

catenacyber is a new contributor to projects/libvpx. The PR must be approved by known contributors before it can be merged. The past contributors are: tysmith, jzern, DonggeLiu, cvediver, Dor1s, sylvestre, posidron (unverified), harishdm (unverified), hho2 (unverified), johannkoenig (unverified)

[catenacyber]

Still needs https://chromium-review.googlesource.com/c/webm/libvpx/+/7205527

[catenacyber]

libvpx build was currently broken due to MSAN see https://oss-fuzz-build-logs.storage.googleapis.com/log-75519bb5-f4c3-422b-b155-68717b7d98c7.txt

[jzern]

cc @wantehchang

libvpx build was currently broken due to MSAN see https://oss-fuzz-build-logs.storage.googleapis.com/log-75519bb5-f4c3-422b-b155-68717b7d98c7.txt

Meaning we see a crash in the nalloc enabled build? That's good.

[catenacyber]

Meaning we see a crash in the nalloc enabled build?

No, meaning the build was broken before (I think nalloc is irrelevant here, every fuzz target crashes)
I do not know why this does not show in https://issues.oss-fuzz.com/u/1/issues?q=libvpx but it is all red in https://oss-fuzz-build-logs.storage.googleapis.com/index.html#libvpx (just showing the past week)

[jzern]

@jeromejj FYI

[jeromejj]

It's a "startup crash" happened during this check:

oss-fuzz/infra/base-images/base-runner/bad_build_check

Line 146 in c72ef09

SKIP_SEED_CORPUS=1 run_fuzzer $FUZZER_NAME -seed=1337 -runs=$MIN_NUMBER_OF_RUNS &>$FUZZER_OUTPUT

[catenacyber]

(MSAN crash may be use of an uninstrumented library such as zlib)

[catenacyber]

@jzern https://chromium-review.googlesource.com/c/webm/libvpx/+/7232054 may be a better fix for nalloc vs MSAN in libvpx