Adds a small new subsection to the section on contributing via coding that highlights the list of issues with partial patches that could be picked up by another contributor.

fix broken link

Part of https://github.com/flutter/flutter/issues/150869.

Part of https://github.com/flutter/flutter/issues/145009

Finishes updating links in the repo that pointed to the old wiki

Mirrored change in the .github/ repo: https://github.com/flutter/.github/pull/34

Today (Jul 17, 2023), I renamed the `good first contribution` label to `good first issue`. This is because
1) `good first issue` is more commonly used for this intent across GitHub and and thus may be (ever so slightly) more recognizable to potential new contributors, and, more importantly,
2) GitHub recognizes the label `good first issue` when surfacing good first issues in specific places in GitHub[^1].

This PR updates Contributing.md to match the new name.

`grep` did not find any other references to `good first contribution` to update in this repo.

[^1]: [Source (GitHub docs)](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels). Example: https://github.com/flutter/flutter/contribute. If my vague memory serves me correctly, this can also appear in certain emails or the "discovery queue"-type experience that GitHub provides.

I found a typo error in CONTRIBUTING.md and fixed it.

* Add more things to CONTRIBUTING.md

* I forgot about QA!

This reverts commit 04ea3183.

This reverts commit e768c92f.

* Update packages.

* Add many more global analyses.

* Catch trailing spaces and trailing newlines in all text files.
  Before we were only checking newly added files, but that means we
  missed some.

* Port the trailing spaces logic to work on Windows too.

* Correct all the files with trailing spaces and newlines.

* Refactor some of the dev/bots logic into a utils.dart library.
  Notably, the "exit" and "print" shims for testing are now usable
  from test.dart, analyze.dart, and run_command.dart.

* Add an "exitWithError" function that prints the red lines and
  then exits. This is the preferred way to exit from test.dart,
  analyze.dart, and run_command.dart.

* More consistency in the output of analyze.dart.

* Refactor analyze.dart to use the _allFiles file enumerating logic
  more widely.

* Add some double-checking logic to the _allFiles logic to catch
  cases where changes to that logic end up catching fewer files
  than expected (helps prevent future false positives).

* Add a check to prevent new binary files from being added to
  the repository. Grandfather in the binaries that we've already
  added.

* Update all the dependencies (needed because we now import crypto in
  dev/bots/analyze.dart).

* Added note about design doc template.

* switched "our" to "flutter"

* updated link

* Update CONTRIBUTING.md

* Update CONTRIBUTING.md

* Mention new gitter channel

* Update CONTRIBUTING.md

* Split analysis steps out of dev/bots/test.dart into dev/bots/analyze.dart.

This allows to run analysis step with command line arguments that are only applicable to flutter analyze(like --dart-sdk, needed for dart-flutter-engine head-head-head bot).

* Add forgotten dev/bots/analyze.dart

* Refactor common code from analyze.dart and test.dart into run_command.dart

* Remove comments, add header

Update CONTRIBUTING.md to suggest Android Studio and fix Mac command to install android-platform-tools. (#19537)

This removes the final traces of Travis and Appveyor from the Flutter tree.

I've updated the documentation and fixed a couple of places where scripts look for Travis, and eliminated the dart tools runningOnTravis function (which was unused anyhow).

There are places in the flutter script that used to look for the environment variable TRAVIS. We actually do want to continue to detect that we're running on Travis there, since in the plugins repo we still use Travis (for the moment). In any case, it's OK, because the CI environment variable is set on all of the CI bots (Cirrus, Travis, and Appveyor).

FastLane doesn't have a setup_cirrus equivalent to setup_travis, but it actually doesn't matter there either, since it doesn't do Travis-specific things, and it also looks for the CI environment variable.

re-write flutter analyze (the single-shot and --flutter-repo) to use the analysis server

Revert "re-write flutter analyze (the single-shot and --flutter-repo) to use the analysis server (#16281)" (#16482)

This reverts commit 2f41ea54.

re-write flutter analyze (the single-shot and --flutter-repo) to use the analysis server

* CONTRIBUTING.md: updates for Dart 2; move parts to flutter/engine

* address comments

* Point to master API docs

I _think_ this is the right place, since people contributing and working on master might care about where the API docs are for master branch.

* Update CONTRIBUTING.md

update from review comment