curator release versions should be populated from the project expansions

we should change the value of curator_release in the server evergreen.yml to use a project expansion, in the form of:

${curator_release|<default_value>)

which will let us move forward and try releases across branches and make the process of updating and experiment with evergreen deploys much easier, particularly during release season.