This also adds a Hifi3z test script.

BUG=http://b/195937824

BUG=http://b/195937824Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>

* Fixes for RISCV build

* Consolidate compiler flags

* Added RISC-V continuous integration script

* Added workflow for RISC-V CI action
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>

Fixes #294

Copy from xtensa ci scripts to run the test script inside of a docker
container.

We use the espressif/idf:release-v4.3 image.

Add a build that builds the full tensorflow-microlite.a library.

The person detection example is more complicated and not fixed here.
Co-authored-by: NMichael O'Cleirigh <michael.ocleirigh@gmail.com>
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>

I copied the sparkfun-edge action and then adjusted to call the esp32 ci test script.

Changed the job name from cortex_m to esp32.

Inserted the Readme entry at the alphabetically appropriate index.
Signed-off-by: NMichael O'Cleirigh <michael.ocleirigh@gmail.com>
Co-authored-by: NMichael O'Cleirigh <michael.ocleirigh@gmail.com>

* modify a tflite file in the tflite-micro repository.

* fix the path

* Update workflow logic to complete workflow without error with NO_CHECK_TFLITE_FILES

* revert change to the tflite files.

* fail PRs that overwrite a set of files from upstream

* Change some names, modify Python script logic etc.

* small fixes.

* Use more restrictive TFLM-bot token.
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>
Co-authored-by: NAdvait Jain <advaitjain@google.com>

* check PR description for a BUG= line

* Changed file name and added some more documentation.

* move the if to be on the steo instead of at the job.

This is to allow for the job to succeed (instead of being skipped) when
the BUG= text is found. And as a result we can have it be a required
status check.
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>
Co-authored-by: NAdvait Jain <advaitjain@google.com>

Similar to https://github.com/actions/checkout/issues/518

* remove ci runner labels from PRs

* moving label deletion to own workflow file

* changing target and removing conditional

* adding comment on error catching
Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>

Following the pattern of #151 and fixes #11.

This is required only because some of the third_party_downloads are
still using the Makefile functions and thus require an explicit
`make third_party_downloads`.

Additionally, we sometimes also want to avoid all downloads and this PR
adds in a flag for that as well.

Fixes #119 and the corresponding internal bug http://b/184886633

Related bugs are http://b/143904317 and http://b/183229719

* Trigger workflow from pull_request_target.
 * Explicitly call third_party_downloads prior to running the tests.

BUG=http://b/190108540

BUG=http://b/190108540

Co-authored-by: NAdvait Jain <advaitjain@users.noreply.github.com>

* remove unnecessary triggers.
 * explicitly specify branch for pull request trigger

Also, deleted some unused config from ci.yml

Since we trigger the CI workflow on any label change, when the cla:yes
label is applied the CI workflow will be run, and there is no way around
that with the current setup.

If the sync PR does not have the ci:run label, the checks will be
skipped but will still need to be run again prior to merge since
skipping the checks invalidates the previous completion of the required checks.

As a result, we are keeping the ci:run label. What this means is that
the reviewer can manually apply the cla:yes label and then start
auto-merge (which will wait for another round of the required checks to
be run).

cla:yes can only be applied by someone from Google, so will be done
manually. However, the goal here is to have the PR be ready to merge
once a Google engineer reviews it.

* Automatically remove the cla: no label and apply cla: yes label.
 * sync PR generation should not error out if there are no changes.

Without the additional step of `git add`, any untracked files will not
be part of the PR that is created with the sync workflow.

Manually tested this change on my fork of tensorflow by removing a file,
pushing it to main and then confirming that the sync workflow does not
add to the PR prior to this change, but does add it to the PR after this
change.

Adding the cla: yes label seems error prone so we are going to stick to
only applying the ci:run label automatically and manually toggle the cla
status.

This should allow the github script step to correctly apply and remove
labels.

This reverts commit 2092fec8.

For some reason the actions dashboard has stopped showing me the name of
the sync workflow. Instead it is showing me the path to the yml file
which is somewhat annoying.

* Added a (presubmit) suffix to all the status checks that shold be
   required prior to merging.
 * trying out automatically removeing the "cla: no" label for the sync
   PRs.