@Nonnull
	public ObservableBoolean getAllowBasicJvmBaseOffsetZeroCheck() {
		return allowBasicJvmBaseOffsetZeroCheck;
	}
When the {@link #getZipStrategy() ZIP strategy} is {@link ZipStrategy#JVM} this allows toggling
how the JVM base offset of the zip file is calculated. Normally the start of a ZIP file is calculated
based off the logic in {@code ZipFile.Source#findEND()} which looks like:
<pre>{@code
 // ENDSIG matched, however the size of file comment in it does
 // not match the real size. One "common" cause for this problem
 // is some "extra" bytes are padded at the end of the zipfile.
 // Let's do some extra verification, we don't care about the
 // performance in this situation.
 byte[] sbuf = new byte[4];
 long cenpos = end.endpos - end.cenlen;
 long locpos = cenpos - end.cenoff;
}</pre>
In some edge cases this results in {@code locpos} being {@code > 0} even when the file has no prefix/padding.

@return {@code true} when defaulting to check for zero being the base JVM zip offset instead of the lookup
based on the code in {@code ZipFile.Source#findEND()}.
recaf-core/src/main/java/software/coley/recaf/services/workspace/io/ResourceImporterConfig.java