Restore pretenuring of HeapNumber literals

This was a regression from 317cf321
which showed up, at least, on Kraken.

Bug: chromium:782150
Change-Id: Ifd69b86c566182f1a50761b67c911bdde2aed997
Reviewed-on: https://chromium-review.googlesource.com/759101Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
Commit-Queue: Adam Klein <adamk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#49238}

src/ast/ast.cc

@@ -821,7 +821,7 @@ Handle<Object> Literal::BuildValue(Isolate* isolate) const {
     case kSmi:
       return handle(Smi::FromInt(smi_), isolate);
     case kHeapNumber:
-      return isolate->factory()->NewNumber(number_);
+      return isolate->factory()->NewNumber(number_, TENURED);
     case kString:
       return string_->string();
     case kSymbol:

src/interpreter/constant-array-builder.cc

@@ -379,7 +379,7 @@ Handle<Object> ConstantArrayBuilder::Entry::ToHandle(Isolate* isolate) const {
     case Tag::kRawString:
       return raw_string_->string();
     case Tag::kHeapNumber:
-      return isolate->factory()->NewNumber(heap_number_);
+      return isolate->factory()->NewNumber(heap_number_, TENURED);
     case Tag::kBigInt:
       // This should never fail: the parser will never create a BigInt
       // literal that cannot be allocated.