Disable editing for certain fields once bundle reaches starting state

[leilenah]

Reasons for making this change

Currently, all bundle fields that aren't generated by CodaLab are editable by the user indefinitely. However, there are certain fields that don't make sense for the user to edit once a bundle has started running, e.g. store.

That being said, there are some fields that do make sense for the user to edit indefinitely such as name and description.

This change locks the following editable fields once a bundle has reached the starting state:

request_docker_image
request_time
request_memory
request_disk
request_cpus
request_gpus
request_queue
request_priority
request_network
exclude_patterns
store
allow_failed_dependencies

All other editable fields outside of the list above will remain editable indefinitely.

Related issues

#4203

Screenshots

Bundle Before starting State

Bundle After starting State

Checklist

• I've added a screenshot of the changes, if this is a frontend change
• I've added and/or updated tests, if this is a backend change
• I've run the pre-commit.sh script
• I've updated docs, if needed

[leilenah]

@percyliang updated

[leilenah]

@percyliang value check updated

[percyliang]

I personally think that the original formatting is easier to read and see all the fields at one glance...what do you think?

[leilenah]

I generally agree, but things like this hurts my heart:

[leilenah]

One option I've been vaguely thinking about is storing the definitions somewhere else. But I don't want to do that in the scope of this PR

[percyliang]

I think putting the definitions here is nice so that everything is in one place. I agree that long lines and weird wrapping is not-ideal either... I only have a weak preference for the single lines, so feel free to wrap if you feel strongly about it.

[percyliang]

Why !list[0]? In general, I'd like to be a bit more strict about the differences between falsy values...

[leilenah]

The tags field returns [''] when there aren't any tags. Didn't want to change that in case doing so would break a bunch of stuff, but can change if you think I should.

[percyliang]

Oh, I see...maybe write that down as a comment - this is something we should fix. No tags should be []!