fix: broken readonly feature in project and catalog controllers

[floreks]

This fixes an issue with project/catalog CRDs that already exist in the API not being marked correctly as readonly.
isAlreadyExist check did not take into account the readonly status flag and during the subsequent reconcile
it was flipping the original readonly: true to readonly: false because project did exist in the API and ID was already synchronized.
Due to this i.e. deleting readonly default project was trying to delete the actual project from the API thus blocking CRD deletion and further service deployment cleanup.

Test Plan

Running controller locally on dev env

Checklist

• If required, I have updated the Plural documentation accordingly.
• I have added tests to cover my changes.
• I have added a meaningful title and summary to convey the impact of this PR to a user.