Add a prefix to bucket name

[RonanMorgan]

Currently we have a conflict between bucket name because in our OVH account we have many environment (production + dev *2). This small refactor prevent this conflicts

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.83%. Comparing base (40cda4a) to head (3a5ebb7).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #382   +/-   ##
=======================================
  Coverage   84.83%   84.83%           
=======================================
  Files          35       35           
  Lines         996      996           
=======================================
  Hits          845      845           
  Misses        151      151           

Flag	Coverage Δ
backend	84.35% <100.00%> (ø)
client	92.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[frgfm]

Thanks! Agree with the fix, but for the sake of limiting the number of env vars, I think we should mutualize this with SERVER_NAME and probably renaming it to INSTANCE_NAME (or by default using socket.gethostname() or something unique to the VM so that we don't have to figure out which prefix isn't being used)

[RonanMorgan]

ok ! I just merged with main and pushed the modification

[frgfm]

thanks! Only one thing to consider: the s3 bucket initialization might be conflicting with this new rule https://github.com/pyronear/pyro-api/blob/main/scripts/localstack/setup-s3.sh

Make sure to test it out before merging 🙏