Deprecate `nomodule` in Bento

### Summary

Currently we publish `module` and `nomodule` versions of Bento runtime as well as components. Modern browsers have supported JavaScript modules for some time now. See https://caniuse.com/es6-module. We should decide a date for this deprecation after which we should stop publishing `nomodule` versions.

### Motivation

Deprecating this will reduce effort to publish `nomodule` versions of Bento runtime and components.

### Impact on Existing Users

Users (i.e. page authors) can continue using the `module` versions which are well supported across modern browsers.

### Alternative Implementation

Use the `module` versions of the Bento runtime and components.

### Additional Context

_No response_

### Notifications

/cc @ampproject/wg-approvers

Start by locating the configuration or entry points that publish Bento runtime and component module and nomodule versions. Review the linked browser-support context and determine the deprecation date and publishing changes needed; done means the project has an agreed date and a clear plan for stopping nomodule releases.

Written by the indexing model from the issue text.