Cache project discovery (performance)

[guw]

As per #8 we seem to spend quite a bit of time in the Eclipse resource tree. Thus, we need to cache IProject references early.

Closes #8.
Replaces #9.

[github-actions]

Test Results

 40 files  ±0   40 suites  ±0   22s ⏱️ +3s
 57 tests ±0   56 ✅ ±0   1 💤 ±0  0 ❌ ±0 
114 runs  ±0  103 ✅ ±0  11 💤 ±0  0 ❌ ±0 

Results for commit fd0c872. ± Comparison against base commit 9f8988a.

♻️ This comment has been updated with latest results.

[guw]

@snjeza I modified the PR slightly to eagerly check for project

[snjeza]

I have tried to import small. Bazel Eclipse throws

org.eclipse.core.runtime.CoreException: Error provisioning project for package 'BazelPackage (//module1) [OPEN]'
	at com.salesforce.bazel.eclipse.ui.wizards.BazelImportWizard.lambda$2(BazelImportWizard.java:86)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2505)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2528)
	at com.salesforce.bazel.eclipse.ui.wizards.BazelImportWizard.lambda$1(BazelImportWizard.java:80)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:123)
Caused by: org.eclipse.core.runtime.CoreException: Unable to find project for Bazel package '//module1' in the Eclipse workspace. Please check the workspace setup!
	at com.salesforce.bazel.eclipse.core.model.BazelPackageInfo.getBazelProject(BazelPackageInfo.java:171)
	at com.salesforce.bazel.eclipse.core.model.BazelPackage.getBazelProject(BazelPackage.java:154)
	at com.salesforce.bazel.eclipse.core.model.discovery.ProjectPerPackageProvisioningStrategy.provisionPackageProject(ProjectPerPackageProvisioningStrategy.java:458)
	at com.salesforce.bazel.eclipse.core.model.discovery.ProjectPerPackageProvisioningStrategy.doProvisionProjects(ProjectPerPackageProvisioningStrategy.java:351)
	at com.salesforce.bazel.eclipse.core.model.discovery.BaseProvisioningStrategy.doProvisionProjects(BaseProvisioningStrategy.java:1224)
	at com.salesforce.bazel.eclipse.core.model.discovery.BaseProvisioningStrategy.provisionProjectsForSelectedTargets(BaseProvisioningStrategy.java:1810)
	at com.salesforce.bazel.eclipse.core.model.SynchronizeProjectViewJob.provisionProjectsForTarget(SynchronizeProjectViewJob.java:546)
	at com.salesforce.bazel.eclipse.core.model.SynchronizeProjectViewJob.runInWorkspace(SynchronizeProjectViewJob.java:718)
	at com.salesforce.bazel.eclipse.core.setup.ImportBazelWorkspaceJob.runInWorkspace(ImportBazelWorkspaceJob.java:146)
	at com.salesforce.bazel.eclipse.ui.wizards.BazelImportWizard.lambda$2(BazelImportWizard.java:81)

[guw]

I think it's not easily possible to avoid doing the project discovery twice during import/creation. I don't want to open the API to allow injecting project from outside (eg., import wizard). Ideally it would rely on resource events entirely.

[snjeza]

@guw you may want to take a look at #16

[snjeza]

I think it's possible to avoid doing the project discovery twice during import/creation. I don't want to open the API to allow injecting project from outside (eg., import wizard). Ideally it would rely on resource events entirely.

@guw it works fine for me.