AzureStack: Fixed incorrect return type and set to long running operation

[deathly809]

Two changes:

1. Fixed wrong return type
2. Added long running operation flag

Before when executed the return type was IpPool which contained no initialized fields.
In addition, this is a long running operation.

Could not test before because RP was unstable when creating Ip Pools and would crash duh to exception.

[msftclas]

@deathly809,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

[azuresdkciprbot]

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/azsadmin/resource-manager/fabric/readme.md
Before the PR: Warning(s): 3 Error(s): 3
After the PR: Warning(s): 3 Error(s): 6

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[azuresdkciprbot]

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/azsadmin/resource-manager/fabric/readme.md
Before the PR: Warning(s): 3 Error(s): 3
After the PR: Warning(s): 3 Error(s): 6

💡 Please review potentially introduced Error(s)/Warning(s): Analysis Report 💡

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

[deathly809]

@jhendrixMSFT Is there an estimate on the time to review/merge?

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-ruby

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-python

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-node