Implement the new casting syntaxes "as" and "as?".

There's a bit of a reshuffle of the ExplicitCastExpr subclasses:
  - The existing ConditionalCheckedCastExpr expression node now represents
"as?". 
  - A new ForcedCheckedCastExpr node represents "as" when it is a
  downcast.
  - CoerceExpr represents "as" when it is a coercion.
  - A new UnresolvedCheckedCastExpr node describes "as" before it has
  been type-checked down to ForcedCheckedCastExpr or CoerceExpr. This
  wasn't a strictly necessary change, but it helps us detangle what's
  going on.

There are a few new diagnostics to help users avoid getting bitten by
as/as? mistakes:
  - Custom errors when a forced downcast (as) is used as the operand
  of postfix '!' or '?', with Fix-Its to remove the '!' or make the
  downcast conditional (with as?), respectively.
  - A warning when a forced downcast is injected into an optional,
  with a suggestion to use a conditional downcast.
  - A new error when the postfix '!' is used for a contextual
  downcast, with a Fix-It to replace it with "as T" with the
  contextual type T.

Lots of test updates, none of which felt like regressions. The new
tests are in test/expr/cast/optionals.swift. 

Addresses <rdar://problem/17000058>


Swift SVN r18556

test/stdlib/NewString.swift

@@ -11,10 +11,10 @@ func hexAddrVal<T>(x: T) -> String {
 
 func hexAddr(x: AnyObject?) -> String {
   if let owner: AnyObject = x {
-    if let y = owner as _StringBuffer._Storage.Storage {
+    if let y = owner as? _StringBuffer._Storage.Storage {
       return ".Native\(hexAddrVal(y))"
     }
-    if let y = owner as NSString {
+    if let y = owner as? NSString {
       return ".Cocoa\(hexAddrVal(y))"
     }
     else {