Dynamically generated textures generated from a "paletted_permutations" atlas source do not copy over resource metadata from their respective base textures.

What I expected to happen was...:
When supplying a base texture to the "textures" field of the "paletted_permutations" atlas source, for it to copy over the resource metadata (contained in an <texture>.png.mcmeta file) of the supplied base texture to the dynamically generated texture, a.k.a. the dynamically generated texture will be animated in the same way as the base texture would be.

What actually happened was...:
The dynamically generated texture gets generated, but it does not take on the resource metadata of the base texture.

Steps to Reproduce:
1. Create a Resource Pack
2.1. Add a "paletted_permutations" atlas source to an existing atlas (blocks is used in the example)
2.2. Add the resource location of an animated texture to the "textures" field of the atlas source, this should be a texture that has a corresponding <texture>png.mcmeta file (base_texture is used in the example)
2.3. Add the resource location of a palette key (palete_key is used in the example)
2.4. Add a permutation in the "permutations" field (blue with 'blue_palette' is used in the example)
2.5. View the dynamically generated texture in the world, i.e. through applying it to a model (block/blue_wool is used in the example)

See "Demonstration Resource Pack" for an example. The blue wool is the dynamically generated outcome, while white wool is the expected outcome (done manually using image editing tools)