feat: implicit convert BooleanT to NumberT

Also adds implicit conversion configuration option to Type constructor,
  and institutes a numbers-only bundle, and supports argument matching
  with implicit conversions.

  Still need to test that a behavior that invokes implicit conversion ends up
  with the conversion operation as a dependency (and so regenerates itself if
  the conversion changes).

src/number/NumberT.js

@@ -2,5 +2,5 @@ import {Type} from '#core/Type.js'
 import {BooleanT} from '#boolean/BooleanT.js'
 
 export const NumberT = new Type(n => typeof n === 'number', {
-    from: [BooleanT]
+    from: [[BooleanT, math => math.number.resolve([BooleanT])]],
 })

src/number/__test__/NumberT.spec.js

@@ -1,5 +1,7 @@
 import assert from 'assert'
 import {NumberT} from '../NumberT.js'
+import {BooleanT} from '#boolean/BooleanT.js'
+import math from '#nanomath'
 
 describe('NumberT Type', () => {
    it('correctly recognizes numbers', () => {
@@ -8,4 +10,10 @@ describe('NumberT Type', () => {
       assert(NumberT.test(Infinity))
       assert(!NumberT.test("3"))
    })
+
+   it('can convert from BooleanT to NumberT', () => {
+      const cnvBtoN = NumberT.from.get(BooleanT)(math)
+      assert.strictEqual(cnvBtoN(true), 1)
+      assert.strictEqual(cnvBtoN(false), 0)
+   })
 })

src/number/__test__/type.spec.js

@@ -4,5 +4,7 @@ import math from '#nanomath'
 describe('number type operations', () => {
    it('converts to number', () => {
       assert.strictEqual(math.number(2.637), 2.637)
+      assert.strictEqual(math.number(true), 1)
+      assert.strictEqual(math.number(false), 0)
    })
 })