Remove job.name unique requirement.

[hulto]

What type of PR is this?

/kind cleanup
/kind api-change

What this PR does / why we need it:

Remove the unique requirement from the job name.
For workflows like running shell scripts against a target I don't always want to update the jobs name.

Which issue(s) this PR fixes:

[codecov]

Codecov Report

Merging #220 (1615d05) into main (519d2fc) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #220      +/-   ##
==========================================
- Coverage   72.30%   72.29%   -0.01%     
==========================================
  Files          82       82              
  Lines        4676     4675       -1     
==========================================
- Hits         3381     3380       -1     
  Misses       1210     1210              
  Partials       85       85              

Impacted Files	Coverage Δ
tavern/ent/schema/job.go	34.78% <ø> (-1.39%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Cictrone]

this will have to be an @KCarretto review as idk if he relies on job name being unique for any backend stuff.

[Cictrone]

Checked with @KCarretto and took a gander at the tavern code and looks like the answer is "no". At that point I think its just @cmp5987 who need to sign off on it.

[cmp5987]

Seems good to me. Based on discussions offline, we may want to have a the UI field have a default population based on tome + param details to reduce some of the frustration of writing descriptive job names.