In some places of our project we are using toMultimap() method which is marked as @Beta and consequently is considered as an unstable API.

See:
https://github.com/google/guava/blob/d7a26416109381a6770681bc6c299567615e8341/guava/src/com/google/common/collect/Multimaps.java#L108

So. There is already 29.0 version of Google Guava. When does it gonna be considered as a "stable API"?
I would provide you more examples of  similar "unstable API" methods from Guava...
final class RegularImmutableMap<K, V> extends ImmutableMap<K, V> {
  @SuppressWarnings("unchecked")
  static final ImmutableMap<Object, Object> EMPTY =
      new RegularImmutableMap<>((Entry<Object, Object>[]) ImmutableMap.EMPTY_ENTRY_ARRAY, null, 0);
  /**
   * Closed addressing tends to perform well even with high load factors. Being conservative here
   * ensures that the table is still likely to be relatively sparse (hence it misses fast) while
   * saving space.
   */
  @VisibleForTesting static final double MAX_LOAD_FACTOR = 1.2;
  /**
   * Maximum allowed false positive probability of detecting a hash flooding attack given random
   * input.
   */
  @VisibleForTesting static final double HASH_FLOODING_FPP = 0.001;
  /**
   * Maximum allowed length of a hash table bucket before falling back to a j.u.HashMap based
   * implementation. Experimentally determined.
   */
  @VisibleForTesting static final int MAX_HASH_BUCKET_LENGTH = 8;
  
  @VisibleForTesting final transient Entry<K, V>[] entries;
  
  private final transient ImmutableMapEntry<K, V>[] table;
  
  private final transient int mask;
  static <K, V> ImmutableMap<K, V> fromEntries(Entry<K, V>... entries) {
    return fromEntryArray(entries.length, entries);
  }
  /**