Merge "Clean up stale MD files for hoststubgen" into main

- More Android specific build files and code are stored in `frameworks/base/Ravenwood.bp`

  `frameworks/base/ravenwood`.

## Directories and files

- `src/`

  HostStubGen tool source code.

- `annotations-src/` See `Android.bp`.

- `helper-framework-buildtime-src/` See `Android.bp`.

- `helper-framework-runtime-src/` See `Android.bp`.

- `helper-runtime-src/` See `Android.bp`.

- `test-tiny-framework/` See `README.md` in it.

- `scripts`

  - `dump-jar.sh`

    A script to dump the content of `*.class` and `*.jar` files.

  - `run-all-tests.sh`

    Run all tests. Many tests may fail, but at least this should run til the end.

    (It should print `run-all-tests.sh finished` at the end)

## Build and run

### Building `HostStubGen` binary

```

m hoststubgen

```

### Run the tests

- Run all relevant tests and test scripts. All of it is expected to pass, and it'll print

  "Ready to submit" at the end.

  However, because some of the script it executes depend on internal file paths to Soong's

  intermediate directory, some of it might fail when something changes in the build system.

  We need proper build system integration to fix them.

```

$ ./scripts/run-all-tests.sh

```

- See also `README.md` in `test-*` directories.

## TODOs, etc

 - Make sure the parent's visibility is not smaller than the member's.

- @HostSideTestNativeSubstitutionClass should automatically add class-keep to the substitute class.

  (or at least check it.)

 - The `HostStubGenTest-framework-test-host-test-lib` jar somehow contain all ASM classes? Figure out where the dependency is coming from.

- At some point, we can move or delete all Android specific code to `frameworks/base/ravenwood`.

  - `helper-framework-*-src` should be moved to `frameworks/base/ravenwood`

  - `test-framework` should be deleted.

# HostStubGen: tiny-framework test

This directory contains a small classes that "simulates" framework.jar, and tests against it.

This test is agnostic to Android, and it doesn't use any android framework code or knowledge.

## How to run

- With `atest`. This is the proper way to run it, but `atest` has known problems that may

  affect the result. If you see weird problems, try the next `run-ravenwood-test` command.

```

$ atest hoststubgen-test-tiny-test

```

- `run-test-manually.sh` also run the test, but it builds the stub/impl jars and the test without

  using the build system. This is useful for debugging the tool.

```

$ ./run-test-manually.sh

```

 No newline at end of file