Standardise subscription logging

[jemrobinson]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).

🚦 Depends on

⤴️ Summary

Replace:

SRE will be deployed to subscription 'My SRE Subscription' ('1e4924cb-a6ae-4193-a847-62f762c6295e')
SRE will be registered in SHM 'myshm.tre.com'
SHM subscription 'dab6dd05-b468-43f2-b629-f669f19714ba'

with

SRE will be deployed to subscription 'My SRE Subscription' (1e4924cb-a6ae-4193-a847-62f762c6295e)
SRE will be registered in SHM 'myshm.tre.com'
SHM is deployed to subscription 'My SHM Subscription' (dab6dd05-b468-43f2-b629-f669f19714ba)

which matches how we log subscriptions elsewhere.

🌂 Related issues

🔬 Tests

[JimMadge]

Looks good, we can get that in for the release if you can fix the tests 👍.

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
data_safe_haven/commands
sre.py
Project Total

This report was generated by python-coverage-comment-action