Implement the "Publish All" button

What exact change we need to do in the UI for 👇?
When conflict IDs exist, these will be marked up differently in the pending changes UI

I guess make text colour red for those that are not in the current list of redux store, but what about for the new items(I mean those are not in the redux store but are there in conflicts as additional item).

BTW it's very rare now we will get conflicts as clicking on Review N changes button now we are refetching pending changes also on every 10 seconds we are fetching.

The blocker is in

From a conversation in slack @soaratul noted there is no owner info in this

Blocker: Not sure how to proceed further? - let's discuss and decide.

{
    "errors": [
        {
            "code": 1,
            "detail": "This item is unexpected.",
            "source": {
                "pointer": "node:3:en"
            },
        },
        {
            "code": 2,
            "detail": "Expected item not present.",
            "source": {
                "pointer": "node:4:en"
            },
            "meta": {
                "entity_type": "node",
                "entity_id": "4",
                "label": "Drupal node Article"
            }
        }
    ]
}

I think what we need to do is include the auto-save key in meta so that you can match it against the records from the pending changes API

I'll open a separate issue for that

#3499791: Errors returned from the publish all endpoint should include the autosave key in the meta

Assigning to me to continue from @soaratul

Clicking publish all should publish changes. It currently doesn't, but it will at least show you an error as to why it can't publish.

There are follow ups

1. As per @tedbow's suggestion in his review: polish handling for errors moved to follow up #3503404: [Needs design] Polish flow for Publish all changes" when receiving conflict errors in response
2. Publishing currently fails on nodes due to an error with the URL alias field #3503347: Unable to create URL aliases with XB enabled due to incorrect validation constraint addition
3. Changes show up immediately when previewing a node in XB #3502902: Only auto-save content entities/PageRegion config entities when there are actual changes: simply previewing incorrectly causes them to appear in "Review x changes"
4. The pending changes API endpoint should list individual regions for global template changes. Currently adding content to a node will show two changes - one for the node and another for the template[#3500390]
   

#14: is this hard-blocked on #3503347: Unable to create URL aliases with XB enabled due to incorrect validation constraint addition?

I did a review (and spotted a few nits) to try to answer #15 myself. AFAICT the answer is "yes".

If so, I propose to postpone this issue on #3503347: Unable to create URL aliases with XB enabled due to incorrect validation constraint addition and I'll prioritize tackling that on Monday.

Well … that was easier than I thought! @longwave did the work, I did the research to prove his fix was correct: #3503347: Unable to create URL aliases with XB enabled due to incorrect validation constraint addition is in!

🎉

🤩

But can we get a short screencast to share this with the world? 🫣🙏

Not pragmatic to await this screenshot anymore, so marking fixed. This'll have to be demonstrated as part of other issues landing, then.