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

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

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.

The corresponding change in upstream TF is: https://github.com/tensorflow/tensorflow/pull/48809

Bug: http://b/184884735

* The tests all pass when run locally, but fail when run via actions.
 * Removed readable_run and directly logging the build ouput since that
   is more convenient with github actions.
 * Separated the two Cortex-M tests into their own individual jobs.

With #25 we went down a path that appeared at first to allow for the checks to be consolidated in an environment variable but ended up being quite complex.

This PR instead modifies the per-job if check to either have the ci:run label or originate not from a pull request.

* Daily build for CI workflow (for buyild badge).
* Separate builds for Sparkfun Edge and COrtex-M for more separation in the build badge.
* Added names to the workflows.
* Manual triggers for all the workflows.

Running these with each PR is not required and additionally results in
the per-PR checks taking longer. As a result, we will run these checks
at a scheduled time (currently once a day) and post a build badge for
these workflows.

Additionally, changed all but one job to directly run from the Ubuntu image (instead of the added indirection of a docker container).

While the parallel jobs should work in theory, and they do when I push to my fork (e.g. advaitjain#2), on the tensorflow/tflite-micro repo, these jobs are queued for a long time.

We will still merge this PR and then investigate why that is the case.

Co-authored-by: NAdvait Jain <advaitjain@google.com>

Transformation between open-source and internal google is complicated by
the code in neon_check.h and since we do not need it for TFLM, we can
instead have the file be empty.

* removed unnecessary bits from tensorflow/BUILD
 * updated the sync script accordingly.
 * using test_all.sh instead of test_all_new.sh from Dockerfile.micro
  (will not update test_all.sh bsed on upstream TF, and will manually
   keep that consistent with upstream TF).

Currently, this script copies the shared TFL/TFLM code as well as the
entire micro sub-folder in Tensorflow. Once TFLM development switches to
using the current repo, the sync script will still be used to get the
shared TFL/TFLM code.

Also, updated the BUILD file to use glob so that there is one less place
to change when a new kernel is ported from TFL to TFLM.

Tested:
 * ran the sync script (which updated reduce.h):
     ```
     ci/sync_from_upstream_tf.sh
     ```
 * confirmed that the docker container can run all the tests
   successfully:
     ```
     docker build -t tflm-test -f ci/Dockerfile.micro .
     docker run --rm tflm-test
     ```

Manually confirmed that the steps in CONTRIBUTING.md work:
```
docker build -t tflm-test -f ci/Dockerfile.micro .
docker run --rm tflm-test
```

Confirmed that the following command passes:
```
./tensorflow/lite/micro/tools/ci_build/test_all_new.sh GITHUB_PRESUBMIT
```