ci: Don't bother mocking os.homedir

Presumably this is to direct the appmap.jar to a known location.
But these tests aren't actually verifying anything about the JAR.
And, every other instance of VSCode that gets launched is going
to also try and update that JAR file in $HOME/.appmap - so we may
as well let these tests do it too.

test/integration/runConfigs/runConfigsJava.test.ts

@@ -24,7 +24,6 @@ describe('run config service in a Java Project', () => {
     await initializeWorkspace();
 
     sinon = createSandbox();
-    sinon.stub(os, 'homedir').returns(ProjectJava);
 
     // This needs to be faked because the Test Runner for Java extension is not installed during testing
     // and VS Code will throw an error when attempting to update an unregistered config ("java.test.config")

test/integration/runConfigs/runConfigsJavaNoTestExt.test.ts

@@ -26,7 +26,6 @@ describe('run config service in a Java Project without the Test Runner for Java
     await initializeWorkspace();
 
     sinon = createSandbox();
-    sinon.stub(os, 'homedir').returns(ProjectJava);
 
     fakeConfigGetSpy = sinon.spy(FakeConfig, 'get');
     fakeConfigUpdateSpy = sinon.spy(FakeConfig, 'update');

test/integration/runConfigs/runConfigsRuby.test.ts

@@ -24,7 +24,6 @@ describe('run config service in a Ruby project', () => {
     await initializeWorkspace();
 
     sinon = createSandbox();
-    sinon.stub(os, 'homedir').returns(ProjectA);
 
     fakeConfigGetSpy = sinon.spy(FakeConfig, 'get');
     fakeConfigUpdateSpy = sinon.spy(FakeConfig, 'update');

test/integration/runConfigs/testConfigsJava.test.ts

@@ -60,7 +60,6 @@ describe('test configs in a Java Project', () => {
 
   beforeEach(async () => {
     sinon = createSandbox();
-    sinon.stub(os, 'homedir').returns(ProjectJava);
 
     fakeConfigGetSpy = sinon.spy(fakeConfig, 'get');
     fakeConfigUpdateSpy = sinon.spy(fakeConfig, 'update');