chore: put export-type enum in separate file

[aberonni]

AB#31009

To be able to use ExportType enum easily in Portalicious, we need to separate it into a file of its own. This should be in line with the 121-service guidelines so it shouldn't be an issue, and is worth the refactor on its own IMHO.

Checklist before requesting a review

• I have performed a self-review of my code
• I have added tests wherever relevant
• I have made sure that all automated checks pass before requesting a review
• I do not need any deviation from our PR guidelines

[jannisvisser]

@aberonni I constantly see 'this change is out of date with main branch', which then prevents being able to merge (or auto-merge from materializing). You have to click 'update branch' then. But if it's not being merged, and then another PR is merged into main, you have to do it again. Is this just how it is?

[aberonni]

@jannisvisser

Is this just how it is?

Pretty much so, yes. It's because of this setting that we enabled a while ago when introducing the PR guidelines:

So if you're in the midst of "PR merging traffic" then you'll have to update the branch a few times before it gets merged.

But tbh, I most of the time leave it to the author to make sure it gets merged.

That said,

You have to click 'update branch' then.

doing that on behalf of the author is fine, but then I would make sure you use the dropdown to select "Update with rebase" rather than update with merge. (It would be great if this could be the default but alas that is not possible).