differences between `remote` actions/sequences and `local` app:dev

## Listing Web and Non-web urls

`Remote`:
- **web**: will show the cdn host
- **non-web**: this shows the `package/action` path for the sequence that is created when an action has `require-adobe-auth:true`
- **non-web**: will always use the adobeioruntime.net host, not the adobeio-static.net cdn host

`Local`:
- **web**: will always show localhost
- **non-web**: this **does not** show the `package/action` path for the sequence that is created when an action has `require-adobe-auth:true`
- **non-web**: since we don't have a cdn for localhost (no point), the host is the same for both web and non-web

## Calling a non-web action/sequence

`Remote`:
- adobeio-static.net cdn: will always return 404
- adobeioruntime.net: will always return 401

`Local`:
- will always return 401

## Calling a web action/sequence: error response object

`Remote`:
- will have both `code` and `error` properties, e.g.
```
{
"code": "7HlbgAP51Dxwagx2jIZYxS4g9a1ZJeW3",
"error": "Response is not valid 'message/http'.",
}
```

`Local`:
- will only have the `error` property, e.g.
```
{
"error": "Response is not valid 'message/http'.",
}
```

Start at the app:dev implementation and reproduce the listed remote and local cases for URL listing, non-web calls, and web-action error responses. The issue does not name files, tests, or a desired behavior, so the intended outcome must first be clarified before completion can be judged.

Written by the indexing model from the issue text.