[Nearby] Report 1:1 transfer status on the C++ side to JS side

A previous CL collaps transfer status on the C++ side.
Only a limit number of transfer status updates are passed through to JS.
This is blocking some testing automation: https://crbug.com/1136365#c19
For example, kComplete is mapped to kInProgress.
This CL map 1:1 for all statuses.

Manually verified using:
Nearby Share tile for receiving a file.
Nearby Share sheet to send a file.
As a sender from Nearby Share sheet, select the receiver at sender side then reject the connection at receiver side.
Run a JS script to register the onTransferUpdate event and check
kComplete can be received when transmission done.

Bug: 1149598
Change-Id: Ic5bfef95b4e51b16fbc895a42aad578840efa2dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2543528Reviewed-by: James Vecore <vecore@google.com>
Commit-Queue: Eric Lin <ericth@google.com>
Cr-Commit-Position: refs/heads/master@{#828607}

chrome/browser/nearby_sharing/nearby_per_session_discovery_manager.cc

@@ -25,6 +25,7 @@ base::Optional<nearby_share::mojom::TransferStatus> GetTransferStatus(
     case TransferMetadata::Status::kAwaitingRemoteAcceptance:
       return nearby_share::mojom::TransferStatus::kAwaitingRemoteAcceptance;
     case TransferMetadata::Status::kComplete:
+      return nearby_share::mojom::TransferStatus::kComplete;
     case TransferMetadata::Status::kInProgress:
       return nearby_share::mojom::TransferStatus::kInProgress;
     case TransferMetadata::Status::kRejected:
@@ -38,11 +39,15 @@ base::Optional<nearby_share::mojom::TransferStatus> GetTransferStatus(
     case TransferMetadata::Status::kNotEnoughSpace:
       return nearby_share::mojom::TransferStatus::kNotEnoughSpace;
     case TransferMetadata::Status::kFailed:
-    case TransferMetadata::Status::kAwaitingRemoteAcceptanceFailed:
       return nearby_share::mojom::TransferStatus::kFailed;
+    case TransferMetadata::Status::kAwaitingRemoteAcceptanceFailed:
+      return nearby_share::mojom::TransferStatus::kAwaitingRemoteAcceptanceFailed;
     case TransferMetadata::Status::kUnknown:
+      return nearby_share::mojom::TransferStatus::kUnknown;
     case TransferMetadata::Status::kConnecting:
+      return nearby_share::mojom::TransferStatus::kConnecting;
     case TransferMetadata::Status::kCancelled:
+      return nearby_share::mojom::TransferStatus::kCancelled;
     case TransferMetadata::Status::kMediaDownloading:
     case TransferMetadata::Status::kExternalProviderLaunched:
       // Ignore all other transfer status updates.

chrome/browser/resources/nearby_share/nearby_confirmation_page.js

@@ -180,6 +180,7 @@ Polymer({
         this.needsConfirmation_ = false;
         break;
       case nearbyShare.mojom.TransferStatus.kInProgress:
+      case nearbyShare.mojom.TransferStatus.kComplete:
         this.fire('close');
         break;
       case nearbyShare.mojom.TransferStatus.kRejected:
@@ -198,6 +199,7 @@ Polymer({
       case nearbyShare.mojom.TransferStatus.kMediaUnavailable:
       case nearbyShare.mojom.TransferStatus.kNotEnoughSpace:
       case nearbyShare.mojom.TransferStatus.kFailed:
+      case nearbyShare.mojom.TransferStatus.kAwaitingRemoteAcceptanceFailed:
         this.errorTitle_ = this.i18n('nearbyShareErrorCantShare');
         this.errorDescription_ = this.i18n('nearbyShareErrorSomethingWrong');
         break;