Add support for Braket Devices enums and S3 buckets

[maliasadi]

Context:
This PR fixes #206 by adding support for

• Braket Devices enums
• user-provided s3_destination_folder in remote calls.

[sc-45094]

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (7f019cd) 99.31% compared to head (ef4c583) 99.31%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #278   +/-   ##
=======================================
  Coverage   99.31%   99.31%           
=======================================
  Files          41       41           
  Lines        7141     7157   +16     
  Branches      377      377           
=======================================
+ Hits         7092     7108   +16     
  Misses         27       27           
  Partials       22       22           

Files Changed	Coverage Δ
frontend/catalyst/pennylane_extensions.py	99.14% <100.00%> (+<0.01%)	⬆️
runtime/lib/backend/common/Utils.hpp	100.00% <100.00%> (ø)
runtime/tests/Test_LightningDriver.cpp	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dime10]

Thanks @maliasadi 🎉

[josh146]

Nice, thanks @maliasadi!

I have a separate question: your ADR on allowing devices to specifying compilation options. Would it be sufficient in allowing this logic here to not be hardcoded into the Catalyst functions?

[maliasadi]

I have a separate question: your ADR on allowing devices to specifying compilation options. Would it be sufficient in allowing this logic here to not be hardcoded into the Catalyst functions?

@josh146 the qml.device method can take any arbitrary keyword arguments and, we may need to embed these kwargs to the generated LLVM IR which will be parsed and used at run time by the runtime. We don't really need to hardcode these kwargs in the frontend if we can capture these kwargs or the device itself communicates these arguments. However, this issue is unique to the Braket devices at the moment and one possible solution is by simply adding a method that returns a dictionaries of device specifications. For the Braket plugin, this's device_arn and s3_destination_folder.

PS. I've included this to the ADR for re-considering it while refactoring the frontend.

[josh146]

Thanks @maliasadi!

However, this issue is unique to the Braket devices at the moment and one possible solution is by simply adding a method that returns a dictionaries of device specifications. For the Braket plugin, this's device_arn and s3_destination_folder.

Over time we will run into this issue with other devices as well. Even lightning has additional options you can pass it -- e.g., for MCMC sampling:

dev = qml.device("lightning.qubit", wires=2, shots=1000, mcmc=True, kernel_name="NonZeroRandom", num_burnin=200)