[Tests] Workaround flakiness issue in EndToEndMetadataTest.testPublishConsume

[lhotari]

Fixes #13750

Motivation

• If the org.apache.bookkeeper.meta.MetadataDrivers class got loaded before org.apache.pulsar.metadata.bookkeeper.BKCluster constructor is called, things would fail.

Modifications

• Set the system properties for metadata-store backend in pom.xml for all pulsar-broker tests as a workaround

[mattisonchao]

@lhotari

Do we need to remove the following code ?

 public BKCluster(String metadataServiceUri, int numBookies) throws Exception { 
     // ----
     System.setProperty("bookkeeper.metadata.bookie.drivers", PulsarMetadataBookieDriver.class.getName()); 
     System.setProperty("bookkeeper.metadata.client.drivers", PulsarMetadataClientDriver.class.getName()); 
    //  ----
 } 

[lhotari]

@lhotari

Do we need to remove the following code ?

 public BKCluster(String metadataServiceUri, int numBookies) throws Exception { 
     // ----
     System.setProperty("bookkeeper.metadata.bookie.drivers", PulsarMetadataBookieDriver.class.getName()); 
     System.setProperty("bookkeeper.metadata.client.drivers", PulsarMetadataClientDriver.class.getName()); 
    //  ----
 } 

No. That makes it work when running in IDEs that don't necessarily pick up maven pom.xml system properties. I'd rather wait for @merlimat 's opinion on a more intrusive fix.

[mattisonchao]

I see, Thanks to your explanation. 👍🏼