Check whether Lapis sufficiently allows ambiguity codes in mutations

[fengelniederhammer]

Related to GenSpectrum/dashboard-components#1064 and GenSpectrum/LAPIS-SILO#1114. Check how Lapis handles this.

[fengelniederhammer]

The advanced queries don't allow ambiguity codes in the "from symbol" of mutations:

LAPIS/lapis/src/main/antlr/org/genspectrum/lapis/model/advancedqueryparser/AdvancedQuery.g4

Lines 72 to 74 in f519c7d

	namedMutationQuery: name ':' mutationQueryFirstSymbol? position mutationQuerySecondSymbol?;
	mutationQueryFirstSymbol: nucleotideSymbol | aaSymbol;
	mutationQuerySecondSymbol: nucleotideSymbol | ambiguousNucleotideSymbol | aaSymbol | ambiguousAaSymbol;

LAPIS/lapis/src/main/antlr/org/genspectrum/lapis/model/advancedqueryparser/AdvancedQuery.g4

Lines 55 to 57 in f519c7d

	singleSegmentedMutationQuery : singleSegmentedMutationQueryFirstSymbol? position singleSegmentedMutationQuerySecondSymbol?;
	singleSegmentedMutationQueryFirstSymbol: nucleotideSymbol;
	singleSegmentedMutationQuerySecondSymbol: possibleAmbiguousNucleotideSymbol;

Normal mutation queries are indifferent to the characters used in the mutations.