Rename `project_ip_pool_list` and `project_ip_pool_view`

[david-crespo]

The names are wrong and misleading. These are silo-scoped lists of IP pools. These operations were named when we originally thought they would be project-scoped, or that we would have both silo- and project-scoped pools.

To fit with the other silo-scoped endpoints, they should probably be called ip_pool_list and ip_pool_view, but currently those are taken by the fleet-scoped IP pool endpoints. There is also already a silo_ip_pool_list which lets the fleet viewer on the silo page list IP pools linked to that silo.

omicron/nexus/external-api/output/nexus_tags.txt

Lines 121 to 122 in 37a2122

	project_ip_pool_list GET /v1/ip-pools
	project_ip_pool_view GET /v1/ip-pools/{pool}

omicron/nexus/external-api/output/nexus_tags.txt

Line 269 in 37a2122

silo_ip_pool_list GET /v1/system/silos/{silo}/ip-pools

omicron/nexus/external-api/output/nexus_tags.txt

Lines 200 to 218 in 37a2122

	API operations found with tag "system/ip-pools"
	OPERATION ID METHOD URL PATH
	ip_pool_create POST /v1/system/ip-pools
	ip_pool_delete DELETE /v1/system/ip-pools/{pool}
	ip_pool_list GET /v1/system/ip-pools
	ip_pool_range_add POST /v1/system/ip-pools/{pool}/ranges/add
	ip_pool_range_list GET /v1/system/ip-pools/{pool}/ranges
	ip_pool_range_remove POST /v1/system/ip-pools/{pool}/ranges/remove
	ip_pool_service_range_add POST /v1/system/ip-pools-service/ranges/add
	ip_pool_service_range_list GET /v1/system/ip-pools-service/ranges
	ip_pool_service_range_remove POST /v1/system/ip-pools-service/ranges/remove
	ip_pool_service_view GET /v1/system/ip-pools-service
	ip_pool_silo_link POST /v1/system/ip-pools/{pool}/silos
	ip_pool_silo_list GET /v1/system/ip-pools/{pool}/silos
	ip_pool_silo_unlink DELETE /v1/system/ip-pools/{pool}/silos/{silo}
	ip_pool_silo_update PUT /v1/system/ip-pools/{pool}/silos/{silo}
	ip_pool_update PUT /v1/system/ip-pools/{pool}
	ip_pool_utilization_view GET /v1/system/ip-pools/{pool}/utilization
	ip_pool_view GET /v1/system/ip-pools/{pool}