Block Hooks API: Creating a navigation post via POST request ignores hooked blocks meta.

[tjcafferkey]

#59875 was introduced to fix a fatal error happening when the user creates a new Navigation by sending a POST request.

An potential bug (if we see it that way) we inherited as a result of this fix was that the next time the Navigation is loaded it will insert hooked blocks. This brings into question whether we should traverse the incoming post_content and generate ignoredHookedBlocks meta for it to prevent insertion of hooked blocks. The issue is that at the time of the request, we don't have a $post->ID to save this data against.

This was discussed in a little more detail here. #60071 (comment)