Add default remotes to manifest - #260

Allows for specifying (default) remotes for git dependencies, for a more concise specification. The new dependency specification more closely resembles Cargo.toml or pyproject.toml. The main difference is that those use predefined defaults (crates.io and PyPI), which are well established registries. In Bender this is not the case, so remotes have to be specified explicitly. This feature is also somewhat inspired from how uv handles multiple indexes (see here).

# Specify git remotes for dependencies. Optional.
remotes:
  pulp:
    url: "https://github.com/pulp-platform"
    default: true # Only required if multiple remotes are specified.

  # Additional non-default remotes (HTTP or SSH).
  openhw: "https://github.com/openhwgroup"
  internal: "[email protected]:internal-repo"

# Other packages this package depends on. Optional.
dependencies:
  # Path dependency.
  axi: { path: "../axi" }

  # Git version dependency from default remote.
  apb: "0.2"

  # Git version dependency from non-default remote.
  fll: { version: "0.8", remote: "internal" }
  
  # Git version dependency with explicit git url.
  ara: { git: "https://github.com/john_doe/ara.git", version: "2" }

The feature is optional and also backward compatible, meaning specifying the full git url is still supported. Furthermore, this short notation is deliberatly not supported for git revision dependencies in order to highlight those dependencies and nudge people to create and use actual releases.

It is also possible to set a different upstream name, in case the repository name is different from the package name:

  floo_noc: {version: "0.7.0", upstream_name: "FlooNoC" }

However, this feature is not advertised in the README.md

Note: The CLI regression tests are failing because I added more dependencies to the Bender.yml, which triggers the audit output.