* Remove uses of deprecated constants
* Change int.parse to int.tryParse where appropriate

With a fix of a path being printed relative instead of absolute.

This reverts commit 57d78cc7.

Add iOS module template

This will enable integration of flutter-views into existing iOS project.

This reverts commit 8be198d8 that broke the build.

Add iOS module template

This will enable integration of flutter-views into existing iOS project.

* Fix readme link to plugin edit instructions

* Fix flutter tools link

Uses the `version` property from the `pubspec.yaml` file to set the corresponding fields in the `local.properties` file respectively in the `Generated.xcconfig` file.

The `--build-name` and `--build-number` options have changed. Now they trump the `version` property from the `pubspec.yaml` file.

If the `version` property is not set and the  `--build-name` and `--build-number` options are not provided, the build command will not change the `local.properties` / `Generated.xcconfig` file.

The new values are not ready for use yet inside Google

* Roll engine to e976be13c51448f89107d082ec81e2b6731671fa

* move away from deprecated constants

Fixes https://github.com/flutter/flutter/issues/12445

This reverts commit b3e4976c.

* Plumb a --strong option through to the front end server and the engine
so that we can run flutter apps in preview-dart-2 and strong mode

* - Address analyzer lint issues
*- correctly set up strong mode option in the case of AOT builds

We thought it would be OK to call the create command offline-only, but it turns out that isn't a great idea because not all of the create template dependencies are cached by running flutter_tool.

This PR makes it go online by default when running pub get after creating a project, and adds an "--offline" flag to the create command so that offline users can use it offline if their cache is warm.

In order to allow offline usage of the create command we need to be able to tell pub not to try and contact the server to see if new versions are available. Since all the versions that create could want are pinned, it shouldn't need to check for new versions.

This reverts commit 9315a79b.

There is an unfortunate interaction with verifyThenRunCommand

Adds a class `PubContext` with a fixed set of allowed values
Make it clear these values should not be changed casually

Fixed one inconsistency already: update_packages vs update_pkgs
Provide more information for verify calls
Eliminate `ctx_` prefix.

* Provide more information in PUB_ENVIRONMENT for `pub get/upgrade`

Should help diagnose and fix https://github.com/dart-lang/pub-dartlang-dart/issues/636

A more future-proof approach to accessing internal package name lint rule description details.

See: https://github.com/dart-lang/linter/issues/654

* Leave a version tag when creating project

* Generalize .version to .metadata

This reverts commit 5b357500.

* fix updrade script; upgrade to the latest package versions

* exclude special dependencies from transitive closure

* fix stack trace handling in flutter_test due to stack_trace change

* change type on _emptyStackTrace

Removed the legacy --plugin option from flutter create.  Fixes #11815.