Registry-related get methods

首先定位 issue 中列出的 Registry、HolderGetter、HolderLookup、RegistryAccess 和 BootstapContext 方法，然后比较 #10 所采用的方法。跟踪 ResourceKey 或 TagKey 参数来自 static 字段的调用点，并识别受影响的局部变量。完成的标准是：在列出的方法中，适用的变量始终使用从这些字段派生的名称。

A lot of the methods on Registry, HolderGetter, HolderLookup, RegistryAccess take ResourceKey as the sole parameter returning something. A lot of the time, those ResourceKey arguments are obtained from static final fields somewhere which makes choosing the name for the local var very easy.

Something like

Holder<Structure> structure1 = registry.getHolder(BuiltinStructures.NETHER_FOSSIL);

can be changed to

Holder<Structure> netherForsilStructure = registry.getHolder(BuiltinStructures.NETHER_FOSSIL);

This is similar to #10 and how the various is and has methods are handled, by looking at the field used in the parameter.

A non-exhaustive list of methods that this could apply to are:

TagKey

• TagKey#create(ResourceKey, ResourceLocation)

ResourceKey

• ResourceKey#create(ResourceKey, ResourceLocation)

Registry

• Registry#get(ResourceKey)
• Registry#getHolder(ResourceKey)
• Registry#getOptional(ResourceKey)
• Registry#getOrThrow(ResourceKey)
• Registry#containsKey(ResourceKey)
• Registry#getHolder(ResourceKey)
• Registry#getTag(TagKey)
• Registry#getTagOrEmpty(TagKey)
• Registry#getOrCreateTag(TagKey)

RegistryAccess, RegistryAccess$Frozen, HolderLookup$Provider

• RegistryAccess#lookup(ResourceKey)
• RegistryAccess#lookupOrThrow(ResourceKey)
• RegistryAccess#registry(ResourceKey)
• RegistryAccess#registryOrThrow(ResourceKey)

HolderGetter, HolderLookup

• HolderGetter#get(ResourceKey)
• HolderGetter#getOrThrow(ResourceKey)
• HolderGetter#get(TagKey)
• HolderGetter#getOrThrow(TagKey)

BootstapContext

(yes there is a typo in Bootstap in the vanilla source)

• Bootstap#register(ResourceKey, Object, Lifecycle)
• Bootstap#register(ResourceKey, Object)
• Bootstap#lookup(ResourceKey)