feat: ensure Bitbucket repo URLs use HTTPS scheme

[maxrake]

This change was made after discovering that Atlassian Compass components
recognize Bitbucket repository URLs only when they are HTTPS: and not
when they are HTTP:, even though that is how the URL is provided when
obtained by getting the BITBUCKET_GIT_HTTP_ORIGIN environment variable
value.

Additionally, the is_token_set function was refactored to adhere to
the new ruff preview rule SIM103. The latest release of ruff
introduced the new linting rule SIM103: needless-bool,
which causes the code in question to fail when run in preview mode. This
change was made now to get ahead of the rule, for when it enforces the
implicit else cases by default. The change was made in a way that
seeks to maintain readability and intent. Type annotations were added to
the affected function as well.

Testing / Screenshots

What a Bitbucket pipeline looks like when run with the changes from this PR:

---

Updating the repo URL manually:

❯ phylum project list -g integrations
Project Name  Project ID                            Repository URL
---TRIMMED---
TestBB        935bdc06-13e8-4ead-a2b7-e679c69b8970  http://bitbucket.org/phylum-maxrake/testbb
---TRIMMED

❯ phylum project update -i 935bdc06-13e8-4ead-a2b7-e679c69b8970 -g integrations -r https://bitbucket.org/phylum-maxrake/testbb
✅ Successfully updated project "935bdc06-13e8-4ead-a2b7-e679c69b8970" (group "integrations"):
      Name: "TestBB" -> "TestBB"
      Repository URL: "http://bitbucket.org/phylum-maxrake/testbb" -> "https://bitbucket.org/phylum-maxrake/testbb"

❯ phylum project list -g integrations
Project Name  Project ID                            Repository URL
---TRIMMED---
TestBB        935bdc06-13e8-4ead-a2b7-e679c69b8970  https://bitbucket.org/phylum-maxrake/testbb
---TRIMMED---

---

Re-running the pipeline: