chore(graphql-api): revert es aliases to generic names

[rileyhgrant]

Importantly, this must be accompanied by the aliases changed in this PR (genes_grch38, gnomad_v4_variants, gnomad_structural_variants_v3, gnomad_v4_cnvs) to already have been re-pointed at the correct indices.

Just did a double check, and the current indices associated with these aliases are:

genes_grch38:             genes_grch38-2024-04-03--12-30
v4p1_genes_grch38:        genes_grch38-2024-04-03--12-30 

gnomad_v4_variants:       gnomad_v4_variants-2024-04-17--20-50   
v4p1_gnomad_v4_variants:  gnomad_v4_variants-2024-04-17--20-50   

gnomad_structural_variants_v3:      phil_demo_gnomad_structural_variants_v3-2024-04-08--18-30 
v4p1_gnomad_structural_variants_v3: phil_demo_gnomad_structural_variants_v3-2024-04-08--18-30 

gnomad_v4_cnvs:           gnomad_v4_cnvs-2024-04-24--20-12
v4p1_gnomad_v4_cnvs:      gnomad_v4_cnvs-2024-04-24--20-12 

So we should be good to merge and deploy this all smoothly.

After this PR is merged and deployed, we can safely drop the 4 aliases indices no longer referenced (the 4 above preprended with v4p1_..., e.g. v4p1_genes_grch38)

There's also some cleaning up of indices and aliases we should probably do, lots of various old indices and aliases floating around

[sjahl]

Looks good to me.

After this PR is merged and deployed, we can safely drop the 4 indices no longer referenced (the 4 above preprended with v4p1_..., e.g. v4p1_genes_grch38)

Just to clarify -- we would be dropping aliases not indices here, right?

[rileyhgrant]

Looks good to me.

After this PR is merged and deployed, we can safely drop the 4 indices no longer referenced (the 4 above preprended with v4p1_..., e.g. v4p1_genes_grch38)

Just to clarify -- we would be dropping aliases not indices here, right?

Whoops, yes you're right, alias not index.