Saving a challenge sets the legacyId to null

[ThomasKranitsas]

I just tried to edit https://challenges.topcoder-dev.com/projects/16531/challenges/14cecae1-2646-43be-8804-d9f4cd668f05/edit and it set the legacyId to null.

The legacyId was previously populated by the legacy processor

cc @rootelement

[vikasrohit]

@ThomasKranitsas is it still happening for you? If yes, I think it is happening because of the root cause of another issue mentioned here topcoder-platform/challenge-api#198 (comment)

[vikasrohit]

@acshields Brining it back from Backlog to keep an eye on it.

[vikasrohit]

@drasticdpk can you please check if it is happening for you?