Add Generators.egressTimeBasedGenerator() method that constructs TimedBasedGenerator with a sensible choice of interface

[pgalbraith]

Take # 2

[cowtowncoder]

Ok, this works better but somehow I get 2 local test failures that look like:

[ERROR] Tests run: 21, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 0.026 s <<< FAILURE! - in com.fasterxml.uuid.EthernetAddressTest
[ERROR] testFromEgressInterface(com.fasterxml.uuid.EthernetAddressTest)  Time elapsed: 0.013 s  <<< FAILURE!
junit.framework.AssertionFailedError
	at com.fasterxml.uuid.EthernetAddressTest.testFromEgressInterface(EthernetAddressTest.java:1323)

[ERROR] testFromEgressInterfaceRoot(com.fasterxml.uuid.EthernetAddressTest)  Time elapsed: 0.002 s  <<< FAILURE!
junit.framework.AssertionFailedError
	at com.fasterxml.uuid.EthernetAddressTest.testFromEgressInterfaceRoot(EthernetAddressTest.java:1316)

meaning, I think, that no "egress" interface is found on my Mac mini somehow.

I won't revert this yet, since I think this is resolvable, and so I hope this can be done.

Thank you once again for the contribution -- sort of exciting to add functionality to something I wrote originally 20 years ago!

[pgalbraith]

Yikes, maybe this is something better left in draft until it can be tested on a wider variety of platforms. @cowtowncoder what JDK are you using?

[cowtowncoder]

@pgalbraith JDK 1.8.0_322 for the most part, although I will now try 11.0.15 to see if that behaves differently.

Ok. So 11.0.15 (tem) has the same issue. Cannot try 17 since compilation (... for now) is for JDK 6.

EDIT Filed #53 for JDK baseline boost as well; not really closely related to this but something that I had thought about earlier.

[pgalbraith]

Ok unfortunately I think the smart thing is to pull this until I can figure out what is happening. I'll write up a little diagnostic to see if we can dump out some useful info for troubleshooting. I briefly considered buying a Mac today, but then decided this wasn't worth risking my marriage :-D ...

[cowtowncoder]

:-D

It's ok, I think -- For now I think I'll just disable two failing tests but keep code around. And obviously won't be releasing anything until we know what to do here.

[cowtowncoder]

Ok, unfortunately I will need to revert this, to be able to release 4.1.0 with other new features.