Moving PackageRepository.Default into its own EnsoPackageRepository

[JaroslavTulach]

Pull Request Description

PackageRepository is a trait, yet its .scala file also includes implementation. While the trait is relatively lightweight, the implementation requires way more heavyweight dependencies. For example it depends on EnsoContext.

If we want to eliminate dependency of Compiler on EnsoContext, we'd rather split the trait and implementation of the package repository into two files and move the newly created EnsoPackageRepository implementation next to EnsoContext (which creates its instance).

Important Notes

This is just a refactoring. Functionally wise the behavior shall remain the same.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• All code follows the
  Scala,
  Java,
• All code has been tested:
  • Unit tests continue to pass

[Akirathan]

Rename this file to DefaultPackageRepository.scala, or rename the class here to EnsoPackageRepository too keep it consistent.

[enso-bot]

Jaroslav Tulach reports a new STANDUP for yesterday (2023-07-26):

Progress: - merged EnsoPackageRepository: #7395

• compute offset: a389ff1
• dicussion with GraalVM guys about (Python) interop
• investigating annotation processors: Invoke all Enso benchmarks via JMH #7101 (comment)
• review: Convert Number.round to Java #7360 (review)
• review AP for benchmarks: Invoke all Enso benchmarks via JMH #7101 (review)
• meetings & standups It should be finished by 2023-07-28.

Next Day: Interop with Python