Modify get server API for migration status and migration type both

[YashviJain01]

🔩 Description: What code changed, and why?

Added Migration id, migration type and migration status for active migration in get server API to show the status on Server page itself.

⛓️ Related Resources

https://chefio.atlassian.net/jira/software/c/projects/STALWART/boards/361?modal=detail&selectedIssue=STALWART-34

👍 Definition of Done

Migration id, migration type and migration status can be fetched in the server page now. If a server has a active migration going on, the migration id and migration type column will be fetched

👟 How to Build and Test the Change

rebuild components/automate-gateway/
rebuild components/infra-proxy-service

Ensure Chef Infra Server is running. If it is not start it with start_chef_server
Add the chef-server test environment credentials and extract the SERVER IDs

Request:
curl --location --request GET 'https://a2-dev.test/api/v0/infra/servers/${server_id}' \--header 'api-token: ${get_admin_token}

Response:

    "server": {
        "id": "test",
        "name": "test",
        "fqdn": "fqdn",
        "ip_address": "",
        "orgs_count": 0,
        "migration_id": "id",
        "migration_type": "tyoe",
        "migration_status": "status"
    }
}

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[netlify]

👷 Deploy Preview for chef-automate processing.

🔨 Explore the source changes: 12f6b48

🔍 Inspect the deploy log: https://app.netlify.com/sites/chef-automate/deploys/61f797e5c6579d00083cdc1d

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
20 Code Smells

5.6% Coverage
1.1% Duplication

[YashviJain01]

Creating a pull request for feature branch