[Security Solution] Asset criticality assignment modal calls API even when the criticality doesn't change

[machadoum]

Describe the bug: When save is pressed on the asset criticality modal it calls the API even when the criticality didn't change.

Kibana/Elasticsearch Stack version: 8.15 (main)

Steps to reproduce:

1. Assign an entity criticality to "unassigned"
2. Save
3. Assign an entity criticality to "unassigned" again
4. Save

Current behavior: It will call the delete API which will fail with a 404

Expected behavior: It shouldn't call the API because the criticality level didn't change

Screenshots (if relevant):

Errors in browser console (if relevant):

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

[machadoum]

@jaredburgettelastic I tested it, and the issue is still happening. But it has a very low impact.