[roll] Roll fuchsia [bt][broadcom] Schedule lease drop after acquire

In some cases, the scheduled lease drop could happen before we acquire
the power lease.  In these cases. we could end up holding a lease for a
very long time if there is no traffic.

Instead, schedule the lease drop after we acquire, and re-schedule it if
we already have a lease.

Original-Original-Bug: 507843415
Test: added test - fx test bt-hci-broadcom-tests
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1618368
Original-Original-Revision: d992116ad773133b9453c543c2d47066d408fbff
GitOrigin-RevId: fed871f5b703d0877848f1b91aacb07225e36eaf
Change-Id: Ie9ea3649f5465fe6c7ac017f23e86ec0d5b80767
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1630696
Cr-Commit-Position: refs/heads/main@{#193666}
1 file changed
tree: 9ee70bbfb58258831d1eb89ecdcf7309a109699c
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.