kernelci.api: refactor user-facing API models

[r-c-n]

Related to kernelci/kernelci-api#433 (that PR depends on this one)

Bring the API models used by the user-facing endpoints from the kernelci-api repo to this one so that they can be used by the kernelci-api code and the helpers in this repo.

Bring the base model definitions here as well into a separate file (models_base.py) so that they can be used by the models here and by the internal kernelci-api models.

[r-c-n]

@JenySadadia gentle ping for this. Approved?

[JenySadadia]

@JenySadadia gentle ping for this. Approved?

Did we get staging results along with kernelci/kernelci-api#433 yet? If yes, what did you do about kernelci package?

[r-c-n]

@JenySadadia gentle ping for this. Approved?

Did we get staging results along with kernelci/kernelci-api#433 yet? If yes, what did you do about kernelci package?

I dropped the staging-skip tag from this, so if staging is still working I guess we're good to go for this one. kernelci/kernelci-api#433 hasn't been tested on staging because it depends on the kernelci package deployment. I think we discussed this before I left, that the order should be:

1. Test this on staging and merge if it's ok
2. Deploy a new kernelci pip package
3. Update the pending kernelci-api PR to use the new kernelci package (or, at least, pick the release branch for the time being)
4. Test kernelci-api PR on staging and merge if it works

We're stuck in 1. I think this can be merged. About 2, I have no idea. @nuclearcat have you updated the kernelci pip package before?

[JenySadadia]

@JenySadadia gentle ping for this. Approved?

Did we get staging results along with kernelci/kernelci-api#433 yet? If yes, what did you do about kernelci package?

I dropped the staging-skip tag from this, so if staging is still working I guess we're good to go for this one. kernelci/kernelci-api#433 hasn't been tested on staging because it depends on the kernelci package deployment. I think we discussed this before I left, that the order should be:

1. Test this on staging and merge if it's ok
2. Deploy a new kernelci pip package
3. Update the pending kernelci-api PR to use the new kernelci package (or, at least, pick the release branch for the time being)
4. Test kernelci-api PR on staging and merge if it works

We're stuck in 1. I think this can be merged. About 2, I have no idea. @nuclearcat have you updated the kernelci pip package before?

I'd rather suggest waiting for the staging results along with dependent API PR. This will enable us to find and fix any issues with this one before merging.

[r-c-n]

I'd rather suggest waiting for the staging results along with dependent API PR. This will enable us to find and fix any issues with this one before merging.

I don't know if we're talking about the same thing but I think we're going in circles now. AFAIK we can't test this in staging along with the related API PR because the API PR depends on this being merged to be tested. The API changes depend on this PR but this PR doesn't depend on the API changes, so this one should go first, and after it's merged we'll be able to test the API PR on staging. Does that make sense?

[r-c-n]

@JenySadadia ok, so the related kernelci-api PR passed the tests when sync'd to this PR: https://github.com/kernelci/kernelci-api/actions/runs/7447272775, https://github.com/kernelci/kernelci-api/actions/runs/7447272771. We can merge this now, then remove the staging-skip tag of the other PR and wait for it to run on staging

[JenySadadia]

@JenySadadia ok, so the related kernelci-api PR passed the tests when sync'd to this PR: https://github.com/kernelci/kernelci-api/actions/runs/7447272775, https://github.com/kernelci/kernelci-api/actions/runs/7447272771. We can merge this now, then remove the staging-skip tag of the other PR and wait for it to run on staging

Could you please resolve the comment about pinning bson version?
We can merge the PR after that.

[r-c-n]

@JenySadadia ok, so the related kernelci-api PR passed the tests when sync'd to this PR: https://github.com/kernelci/kernelci-api/actions/runs/7447272775, https://github.com/kernelci/kernelci-api/actions/runs/7447272771. We can merge this now, then remove the staging-skip tag of the other PR and wait for it to run on staging

Could you please resolve the comment about pinning bson version? We can merge the PR after that.

Done

[JenySadadia]

LGTM.